CVE-2024-54428
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 onigetoc Add image to Post add-image-to-post allows Stored XSS.This issue affects Add image to Post: from n/a through <= 0.6.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the onigetoc WordPress plugin's 'Add image to Post' functionality allows attackers to inject Stored XSS payloads through crafted malicious requests. The vulnerability stems from missing anti-CSRF protection in the plugin's image addition forms, enabling attackers to trick authenticated administrators into unknowingly submitting requests that inject malicious scripts into posts.
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.
-
Check if onigetoc plugin is installedLook for the plugin directory at wp-content/plugins/onigetoc/ or search for 'onigetoc' in the WordPress plugins admin panelAffected if The plugin directory exists or the plugin appears in the WordPress installed plugins list
-
Identify the installed plugin versionOpen wp-content/plugins/onigetoc/readme.txt or the main plugin PHP file and locate the version number in the header commentAffected if The version cannot be confirmed as patched or is older than the current stable release
-
Verify the 'Add image to Post' functionality existsIn WordPress admin, navigate to the plugin settings or check if there is a form/button labeled 'Add image to Post' or similar in post editorAffected if The functionality is present and accessible to administrators
-
Check for missing anti-CSRF protection in form handlingExamine the plugin PHP files for form submissions: search for the function handling the 'Add image to Post' action and verify if wp_verify_nonce() or check_admin_referer() is called before processingAffected if The form processing code does not validate nonces or admin referer
-
Inspect posts for injected malicious scriptsQuery the wp_posts table for posts containing suspicious script tags, img onerror attributes, or JavaScript: URIs, particularly in post content fieldsAffected if Malicious scripts are found stored in post content that were not intentionally added by administrators
A user is affected if the onigetoc plugin is installed with the vulnerable functionality present and the plugin code lacks nonce verification in its form handling, or if malicious scripts are already stored in post content.
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 dataUpgrade to a patched version of the plugin; if unavailable, implement nonces/tokens in the plugin's forms to validate request origin, and disable the plugin until a fix is available.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54428 — 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-54428 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