CVE-2024-54398
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 jcaruso001 Flaming Forms flaming-forms allows Stored XSS.This issue affects Flaming Forms: from n/a through <= 1.0.1.
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 Flaming Forms WordPress plugin allows attackers to trick authenticated users into submitting malicious form data that gets stored with unescaped output, leading to Stored XSS. When other users view the compromised form submissions, the injected JavaScript executes in their browsers.
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.
-
Verify Flaming Forms plugin is installedGo to WordPress admin > Plugins and look for 'Flaming Forms' in the installed plugins list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%flaming-forms%';Affected if Plugin is installed and active
-
Identify installed plugin versionIn WordPress admin, click on the Flaming Forms plugin to view its details, or check the plugin header in wp-content/plugins/flaming-forms/*.php for the 'Version' comment, or query: SELECT meta_value FROM wp_postmeta WHERE meta_key = 'version' AND post_id IN (SELECT ID FROM wp_posts WHERE post_type = 'flaming_forms');Affected if Version cannot be determined or is earlier than the patched release
-
Confirm form submissions existCheck if any forms created with Flaming Forms have submission data stored in the WordPress database: SELECT * FROM wp_posts WHERE post_type LIKE '%form%' OR post_type LIKE '%submission%'; You can also check the plugin's settings or submitted entries view if available in admin.Affected if Form submissions exist in the database
-
Inspect form submission handling for CSRF protectionExamine the plugin files (typically in includes/ or submit-handler.php within the plugin directory) for nonce verification: grep -r 'wp_verify_nonce' or grep -r 'check_admin_referer' in the plugin folder. Also check form templates for nonce fields: grep -r 'wp_nonce_field'Affected if No nonce verification found in form submission handlers or no nonce fields in form templates
If Flaming Forms is installed, forms have submissions stored, and no CSRF nonce protection is found in the submission handling code, the environment is likely vulnerable to CVE-2024-54398.
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 (nonces) for all form submissions and apply proper output encoding/sanitization to prevent stored XSS execution.
- 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-54398 — 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-54398 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