CVE-2025-5537: The Lightbox & Modal Popup WordPress Plugin – FooBox plugin for WordPress is vulnerable to Stored Cross-Site S

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

foobox: upgrade to 2.7.35. Exact commands for each OS are on this page.

Q: Is CVE-2025-5537 being exploited?

CVE-2025-5537 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-5537 affect?

CVE-2025-5537 affects foobox. Severity is medium (CVSS 6.4). The Lightbox & Modal Popup WordPress Plugin – FooBox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via image alternative texts in all versions up to, and including, 2.7.34 due to insufficient input sanitization and outpu

Q: How urgent is CVE-2025-5537?

Priority 25/100. No elevated risk signals yet.

Routine

MEDIUM 6.4UPGRADE

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

The Lightbox & Modal Popup WordPress Plugin – FooBox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via image alternative texts in all versions up to, and including, 2.7.34 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 90%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-07-08
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: fooplugins

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

Am I affected?

Timeline

2025-07-08 05:15 UTCPublished CVE record published
2026-06-17 09:48 UTCUpdated Record last modified

fooplugins foobox UPGRADE

Affected: < 2.7.35

Fixed in: 2.7.35

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 2.7.35 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade foobox

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-5537?

foobox: upgrade to 2.7.35. Exact commands for each OS are on this page.

Is CVE-2025-5537 being exploited?

CVE-2025-5537 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-5537 affect?

CVE-2025-5537 affects foobox. Severity is medium (CVSS 6.4). The Lightbox & Modal Popup WordPress Plugin – FooBox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via image alternative texts in all versions up to, and including, 2.7.34 due to insufficient input sanitization and outpu

How urgent is CVE-2025-5537?

Priority 25/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-5668 MEDIUM 6.4 UPGRADE The Lightbox & Modal Popup WordPress Plugin – FooBox plugin for WordPress is vulnerable to DOM-based Stored Cr
CVE-2024-3276 MEDIUM 4.8 UPGRADE The Lightbox & Modal Popup WordPress Plugin WordPress plugin before 2.7.28, foobox-image-lightbox-premium Wor

References

← Back to latest CVEs