CVE-2024-4957: The Frontend Checklist WordPress plugin through 2.3.2 does not sanitise and escape some of its settings, which

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

frontend checklist: upgrade to newer than 2.3.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-4957 being exploited?

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

CVE-2024-4957 affects frontend checklist. Severity is medium (CVSS 4.3). The Frontend Checklist WordPress plugin through 2.3.2 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 capab

Q: How urgent is CVE-2024-4957?

Priority 27/100. Public exploit reference

Routine

MEDIUM 4.3UPGRADE

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

The Frontend Checklist WordPress plugin through 2.3.2 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.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-06-26
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: j-breuer

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

Am I affected?

Timeline

2024-06-26 06:15 UTCPublished CVE record published
2026-06-17 08:03 UTCUpdated Record last modified

j-breuer frontend checklist UPGRADE

Affected: <= 2.3.2

Fixed in: newer than 2.3.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy frontend-checklist || rpm -q frontend-checklist || frontend-checklist --version

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

sudo apt update && sudo apt install --only-upgrade frontend-checklist

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade frontend-checklist

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

frontend checklist: upgrade to newer than 2.3.2. Exact commands for each OS are on this page.

Is CVE-2024-4957 being exploited?

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

CVE-2024-4957 affects frontend checklist. Severity is medium (CVSS 4.3). The Frontend Checklist WordPress plugin through 2.3.2 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 capab

How urgent is CVE-2024-4957?

Priority 27/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-4959 MEDIUM 4.8 UPGRADE The Frontend Checklist WordPress plugin through 2.3.2 does not sanitise and escape some of its settings, which

References

← Back to latest CVEs