CVE-2025-1033: The Badgearoo WordPress plugin through 1.0.14 does not sanitise and escape some of its settings, which could a

Q: How do I fix CVE-2025-1033?

badgearoo: upgrade to newer than 1.0.14. Exact commands for each OS are on this page.

Q: Is CVE-2025-1033 being exploited?

CVE-2025-1033 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-1033 affect?

CVE-2025-1033 affects badgearoo. Severity is medium (CVSS 4.8). The Badgearoo WordPress plugin through 1.0.14 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is

Q: How urgent is CVE-2025-1033?

Priority 27/100. Public exploit reference

Routine

MEDIUM 4.8UPGRADE

CVE-2025-1033 is a medium-severity flaw (CVSS 4.8) affecting badgearoo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Badgearoo WordPress plugin through 1.0.14 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.8 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-05-15
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: danielpowney

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-15 20:16 UTCPublished CVE record published
2026-06-17 08:38 UTCUpdated Record last modified

danielpowney badgearoo UPGRADE

Affected: <= 1.0.14

Fixed in: newer than 1.0.14

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy badgearoo || rpm -q badgearoo || badgearoo --version

2. UPGRADE to newer than 1.0.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade badgearoo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade badgearoo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-1033?

badgearoo: upgrade to newer than 1.0.14. Exact commands for each OS are on this page.

Is CVE-2025-1033 being exploited?

CVE-2025-1033 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-1033 affect?

CVE-2025-1033 affects badgearoo. Severity is medium (CVSS 4.8). The Badgearoo WordPress plugin through 1.0.14 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is

How urgent is CVE-2025-1033?

Priority 27/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-13828 MEDIUM 6.1 UPGRADE The Badgearoo WordPress plugin through 1.0.14 does not sanitise and escape a parameter before outputting it ba

References

← Back to latest CVEs