CVE-2024-13501: The WP-FormAssembly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'formas

Q: How do I fix CVE-2024-13501?

wp-formassembly: upgrade to newer than 2.0.11. Exact commands for each OS are on this page.

Q: Is CVE-2024-13501 being exploited?

CVE-2024-13501 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-2024-13501 affect?

CVE-2024-13501 affects wp-formassembly. Severity is medium (CVSS 6.4). The WP-FormAssembly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'formassembly' shortcode in all versions up to, and including, 2.0.11 due to insufficient input sanitization and output escaping on user

Q: How urgent is CVE-2024-13501?

Priority 31/100. No elevated risk signals yet.

Routine

MEDIUM 6.4UPGRADE

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

The WP-FormAssembly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'formassembly' shortcode in all versions up to, and including, 2.0.11 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

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.4% (top 67%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-02-18
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: formassembly

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

Am I affected?

Timeline

2025-02-18 05:15 UTCPublished CVE record published
2026-06-17 07:02 UTCUpdated Record last modified

formassembly wp-formassembly UPGRADE

Affected: <= 2.0.11

Fixed in: newer than 2.0.11

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-formassembly || rpm -q wp-formassembly || wp-formassembly --version

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

sudo apt update && sudo apt install --only-upgrade wp-formassembly

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-formassembly

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-2024-13501?

wp-formassembly: upgrade to newer than 2.0.11. Exact commands for each OS are on this page.

Is CVE-2024-13501 being exploited?

CVE-2024-13501 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-2024-13501 affect?

CVE-2024-13501 affects wp-formassembly. Severity is medium (CVSS 6.4). The WP-FormAssembly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'formassembly' shortcode in all versions up to, and including, 2.0.11 due to insufficient input sanitization and output escaping on user

How urgent is CVE-2024-13501?

Priority 31/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs