⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.4

How to Fix CVE-2026-3034: Cross-site scripting in OoohBoi Steroids for Elementor

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-3034 is a cross-site scripting in sagarpatel124 OoohBoi Steroids for Elementor. The fix is to apply the vendor patch noted below.

⚡ At a glance
Severity6.4 (Medium)
Actively exploited?No public listing in CISA KEV
AffectedOoohBoi Steroids for Elementor 0 to <=2.1.24
Fixed inSee vendor advisory
Type (CWE)CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

What is CVE-2026-3034?

The OoohBoi Steroids for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the _ob_spacerat_link, _ob_bbad_link, and _ob_teleporter_link URL parameters in all versions up to, and including, 2.1.24. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user clicks on the injected element. The CVSS base score is 6.4 (Medium). The official advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/9c2de78e-8530-416b-adef-e2e8ff322802?source=cve.

Am I affected?

Check the version of OoohBoi Steroids for Elementor you are running and compare it against the Affected row above (OoohBoi Steroids for Elementor 0 to <=2.1.24). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s ooohboi-steroids-for-elementor 2>/dev/null | grep -i ^Version
rpm -q ooohboi-steroids-for-elementor 2>/dev/null
command -v ooohboi-steroids-for-elementor >/dev/null && ooohboi-steroids-for-elementor --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*OoohBoi Steroids for Elementor*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "OoohBoi Steroids for Elementor" 2>$null

How to fix CVE-2026-3034

Upgrade OoohBoi Steroids for Elementor to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade ooohboi-steroids-for-elementor
dpkg -s ooohboi-steroids-for-elementor | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh ooohboi-steroids-for-elementor -y
# or for older releases:
sudo yum update ooohboi-steroids-for-elementor -y
rpm -q ooohboi-steroids-for-elementor

SUSE / openSUSE


sudo zypper refresh
sudo zypper update ooohboi-steroids-for-elementor
rpm -q ooohboi-steroids-for-elementor

PHP / Composer


composer update sagarpatel124/ooohboi-steroids-for-elementor 2>/dev/null || composer update
composer show | head -20

WordPress


# Update via WP-CLI
wp plugin update --all
wp core update

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-3034 affecting OoohBoi Steroids for Elementor
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-3034-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*OoohBoi Steroids for Elementor*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\ooohboi-steroids-for-elementor-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\OoohBoi Steroids for Elementor" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "OoohBoi Steroids for Elementor" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "OoohBoi Steroids for Elementor"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-3034 affecting OoohBoi Steroids for Elementor
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-3034-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s ooohboi-steroids-for-elementor 2>/dev/null | grep -i ^Version || echo "ooohboi-steroids-for-elementor not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q ooohboi-steroids-for-elementor || echo "ooohboi-steroids-for-elementor not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-3034-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/ooohboi-steroids-for-elementor /etc/ooohboi-steroids-for-elementor.d /etc/ooohboi-steroids-for-elementor.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y ooohboi-steroids-for-elementor
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y ooohboi-steroids-for-elementor
elif command -v yum >/dev/null; then
    yum update -y ooohboi-steroids-for-elementor
elif command -v zypper >/dev/null; then
    zypper --non-interactive update ooohboi-steroids-for-elementor
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s ooohboi-steroids-for-elementor 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q ooohboi-steroids-for-elementor
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-3034" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-3034"

Disable the affected service (Linux)


sudo systemctl stop ooohboi-steroids-for-elementor 2>/dev/null || true
sudo systemctl disable ooohboi-steroids-for-elementor 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s ooohboi-steroids-for-elementor 2>/dev/null | grep -i ^Version
rpm -q ooohboi-steroids-for-elementor 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*OoohBoi Steroids for Elementor*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-3034 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-3034?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-3034?

6.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N.

Where is the official advisory for CVE-2026-3034?

The vendor advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/9c2de78e-8530-416b-adef-e2e8ff322802?source=cve. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3034.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*