CVE-2024-32550
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 BMI Adult & Kid Calculator allows Stored XSS.This issue affects BMI Adult & Kid Calculator: from n/a through 1.2.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 · high confidenceA CSRF vulnerability in the BMI Adult & Kid Calculator plugin allows attackers to inject malicious scripts through Stored XSS. By tricking authenticated users into visiting crafted pages, attackers can permanently embed malicious JavaScript that executes whenever other users access the affected functionality.
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 BMI Adult & Kid Calculator plugin is installedCheck your WordPress site's wp-content/plugins directory for a folder named 'bmi-adult-kid-calculator' or similar, or list installed plugins via WP admin panelAffected if The plugin folder exists in your WordPress installation
-
Check installed plugin versionAccess the plugin in WordPress admin under Plugins > Installed Plugins and locate the version number for BMI Adult & Kid Calculator, or inspect the plugin's main PHP file for the 'Version' header commentAffected if The version number is lower than the patched version released for CVE-2024-32550
-
Confirm plugin is activeIn WordPress admin, verify the BMI Adult & Kid Calculator plugin shows as 'Active' under Plugin statusAffected if The plugin is currently active and accessible to users
-
Inspect plugin forms for CSRF protectionView the page containing the BMI calculator shortcode or widget. Use browser developer tools to examine the HTML of any forms. Look for 'nonce' fields or CSRF tokens in the form markupAffected if The plugin forms lack nonce fields or CSRF token inputs, making them vulnerable to CSRF attacks
-
Check for malicious script injection in stored dataIf your plugin stores user input in the database (wp_postmeta or custom tables), query for any entries containing script tags, javascript:, or on* event handlers. Also inspect saved calculator results for unexpected contentAffected if The database contains suspicious script tags or JavaScript event handlers embedded in plugin-related records
You are affected if the BMI Adult & Kid Calculator plugin is installed, active, lacks CSRF protection in its forms, and either runs a vulnerable version or already contains injected malicious scripts in stored data.
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 dataUpdate BMI Adult & Kid Calculator to the latest patched version. If no update is available, implement anti-CSRF tokens in forms and ensure all user inputs are properly sanitized and output-encoded.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32550 — 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-32550 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