CVE-2024-3903: The Add Custom CSS and JS WordPress plugin through 1.20 does not have CSRF check in some places, and is missin

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

add custom css and js: upgrade to newer than 1.20. Exact commands for each OS are on this page.

Q: Is CVE-2024-3903 being exploited?

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

CVE-2024-3903 affects add custom css and js. Severity is high (CVSS 7.1). The Add Custom CSS and JS WordPress plugin through 1.20 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in as author and above add Stored XSS payloads via

Q: How urgent is CVE-2024-3903?

Priority 33/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2024-3903 is a high-severity flaw (CVSS 7.1) affecting add custom css and js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Add Custom CSS and JS WordPress plugin through 1.20 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in as author and above add Stored XSS payloads via a CSRF attack

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 88%)
CISA exploited list	No
Weakness	CWE-352
Published	2024-05-14
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: technologicx

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

Am I affected?

Timeline

2024-05-14 15:42 UTCPublished CVE record published
2026-06-17 07:45 UTCUpdated Record last modified

technologicx add custom css and js UPGRADE

Affected: <= 1.20

Fixed in: newer than 1.20

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy add-custom-css-and-js || rpm -q add-custom-css-and-js || add-custom-css-and-js --version

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

sudo apt update && sudo apt install --only-upgrade add-custom-css-and-js

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade add-custom-css-and-js

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

add custom css and js: upgrade to newer than 1.20. Exact commands for each OS are on this page.

Is CVE-2024-3903 being exploited?

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

CVE-2024-3903 affects add custom css and js. Severity is high (CVSS 7.1). The Add Custom CSS and JS WordPress plugin through 1.20 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in as author and above add Stored XSS payloads via

How urgent is CVE-2024-3903?

Priority 33/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs