CVE-2025-3510: The tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple shortcodes

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

composer: upgrade to 5.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2025-3510 being exploited?

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

CVE-2025-3510 affects composer. Severity is medium (CVSS 6.4). The tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple shortcodes in all versions up to, and including, 5.4 due to insufficient input sanitization and output escaping on user supplied attributes.

Q: How urgent is CVE-2025-3510?

Priority 28/100. No elevated risk signals yet.

Routine

MEDIUM 6.4UPGRADE

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

The tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple shortcodes in all versions up to, and including, 5.4 due to insufficient input sanitization and output escaping on user supplied attributes. 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 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.3% (top 79%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-05-02
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: tagdiv

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

Am I affected?

Timeline

2025-05-02 04:15 UTCPublished CVE record published
2026-06-17 09:20 UTCUpdated Record last modified

tagdiv composer UPGRADE

Affected: < 5.4.1

Fixed in: 5.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 5.4.1 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade composer

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

composer: upgrade to 5.4.1. Exact commands for each OS are on this page.

Is CVE-2025-3510 being exploited?

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

CVE-2025-3510 affects composer. Severity is medium (CVSS 6.4). The tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple shortcodes in all versions up to, and including, 5.4 due to insufficient input sanitization and output escaping on user supplied attributes.

How urgent is CVE-2025-3510?

Priority 28/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2026-40261 HIGH 8.8 UPGRADE Composer is a dependency manager for PHP
CVE-2026-40176 HIGH 7.8 UPGRADE Composer is a dependency manager for PHP
CVE-2025-67746 MEDIUM 4.3 UPGRADE Composer is a dependency manager for PHP
CVE-2024-24821 HIGH 8.8 UPGRADE Composer is a dependency Manager for the PHP language

References

← Back to latest CVEs