CVE-2025-24756
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 mgplugin Roi Calculator roi-calculator allows Stored XSS.This issue affects Roi Calculator: 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 · high confidenceCSRF vulnerability in mgplugin Roi Calculator allows authenticated users to be tricked into submitting forms that store malicious JavaScript, resulting in Stored XSS. The lack of CSRF token validation on form submissions enables attackers to craft malicious requests that execute in victim 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 mgplugin Roi Calculator is installedAccess WordPress admin plugins page or check wp-content/plugins directory for 'mgplugin-roi-calculator' or similar folder name. Note the installed version from the plugins list.Affected if Plugin is installed and active in WordPress
-
Compare installed version to any known affected versionsDocument the exact version number found. Check the plugin's readme.txt or main PHP file for version definition. Since no specific version range is provided in this CVE, treat any version of mgplugin Roi Calculator as potentially affected if the ROI Calculator form functionality exists.Affected if Installed version lacks CSRF protection in form handling
-
Confirm ROI Calculator form is accessibleNavigate to the plugin settings or front-end area where the ROI Calculator form is presented. This is typically found in the plugin's admin settings page or a published page with the calculator.Affected if The ROI Calculator form exists and accepts user input
-
Check for missing CSRF token in form submissionsView the page source of the ROI Calculator form. Look for a hidden input field containing a nonce value (typically named _wpnonce, _wpnonce_ACTION, or similar) or verify that form submissions do not trigger WordPress nonce validation in the plugin code.Affected if Form HTML lacks _wpnonce hidden field AND plugin code does not call wp_verify_nonce or check_admin_referer on submission
User is affected if the mgplugin Roi Calculator plugin is installed with its ROI Calculator form accessible and the form submission lacks CSRF token validation.
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 CSRF token validation (wp_nonce_field/check_admin_referer) on all form submissions and apply proper input sanitization and output encoding to prevent XSS.
- Consultation2.0 h
- Implementation6.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24756 — 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-2025-24756 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