CVE-2025-23660
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 waltercerrudo MFPlugin mfplugin allows Stored XSS.This issue affects MFPlugin: from n/a through <= 1.3.
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 MFPlugin version <= 1.3 allows attackers to craft malicious requests that inject persistent malicious scripts (Stored XSS) into the application. The lack of CSRF token validation on state-changing operations enables attackers to trick authenticated users into submitting forms that store XSS payloads, which then execute for other users viewing the affected content.
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.
-
Identify MFPlugin versionLocate the MFPlugin installation and check its version identifier (typically in plugin metadata, manifest file, or about页面). Compare this version number against the affected range: version 1.3 and below.Affected if The installed version of MFPlugin is 1.3 or lower.
-
Inspect state-changing forms for CSRF tokensExamine the HTML source of forms that perform state-changing operations (e.g., settings updates, content submissions, user actions). Look for a hidden input field or header containing a CSRF token value, and verify the token is validated server-side on submission.Affected if State-changing forms lack a CSRF token field or the token is not validated server-side.
-
Test CSRF protection on sensitive endpointsSubmit a crafted request to a state-changing endpoint without including a valid CSRF token. Observe whether the request is accepted and the state change is processed.Affected if Requests without valid CSRF tokens are accepted and result in state changes.
-
Check for input sanitization on stored contentReview the application's code that handles storing user-submitted content. Determine whether input validation, sanitization, or output encoding is applied before storing and rendering content.Affected if User-submitted content is stored and displayed without sanitization or encoding, allowing script injection.
-
Verify Origin/Referer header validationInspect server-side validation of the Origin or Referer HTTP headers on state-changing requests. Determine if requests from unexpected origins are rejected.Affected if The application does not validate Origin or Referer headers on state-changing operations.
If MFPlugin version 1.3 or lower is installed AND state-changing forms lack CSRF token validation AND user-submitted content is rendered without proper sanitization, the environment is affected by this Stored XSS via CSRF 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 (synchronizer token pattern) on all state-changing forms and validate the Origin/Referer headers. Additionally, apply proper output encoding and input sanitization to prevent the Stored XSS component.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23660 — 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-23660 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