CVE-2024-54427
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in ljmacphee Category of Posts list-one-category-of-posts allows Stored XSS.This issue affects Category of Posts: from n/a through <= 1.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA CSRF vulnerability in the Category of Posts WordPress plugin (ljmacphee) allows attackers to craft malicious requests that result in Stored XSS. The 'list-one-category-of-posts' functionality lacks proper anti-CSRF tokens, enabling authenticated administrators to be tricked into submitting requests that inject malicious scripts into the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Category of Posts plugin installationCheck the WordPress wp-content/plugins directory for a folder named 'category-of-posts' or 'ljmacphee-category-of-posts'. Alternatively, in the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Category of Posts' by ljmacphee.Affected if The plugin is installed and active in WordPress
-
Identify the installed plugin versionIn the WordPress admin, click on the plugin name to view its details, or open the main plugin PHP file (usually category-of-posts.php) and look for the 'Version' header comment in the file. Alternatively, check the plugin row in the Plugins list for the version number.Affected if The version number cannot be verified against a patched release, indicating potential vulnerability
-
Verify if the list-one-category-of-posts functionality existsSearch the plugin files for the string 'list-one-category-of-posts' - this may appear as a shortcode, function name, or template. Check the plugin's main PHP file and any shortcode or template files it contains.Affected if The functionality is present in the plugin code, meaning the vulnerable feature exists
-
Check for nonce or CSRF token implementation in the pluginExamine the plugin's PHP files, particularly any handlers for saving settings or processing form submissions related to category listings. Look for calls to 'wp_verify_nonce', 'check_admin_referer', or similar nonce verification functions within functions that handle the list-one-category-of-posts feature.Affected if No nonce verification is found in the code paths that handle the category post listing functionality
If the Category of Posts plugin by ljmacphee is installed and the list-one-category-of-posts functionality is in use without evidence of nonce verification in its handling code, the environment is likely affected by this CSRF-to-Stored XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens (nonce verification) on all state-changing operations in the plugin, particularly the category post listing functionality, and ensure proper input validation and output escaping for stored content.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54427 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54427 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data