CVE-2025-31401
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 mmetrodw MMX – Make Me Christmas mmx-make-me-christmas allows Stored XSS.This issue affects MMX – Make Me Christmas: from n/a through <= 1.0.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 · moderate confidenceA CSRF vulnerability in the MMX – Make Me Christmas WordPress plugin allows attackers to craft malicious requests that result in stored XSS. By tricking an authenticated administrator into visiting a crafted page, attackers can inject malicious scripts that persist and execute when other users view 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.
-
Verify MMX plugin is installedGo to WordPress Admin > Plugins and look for 'MMX - Make Me Christmas' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Check installed versionClick on the plugin to view details, or check the plugin files in wp-content/plugins/ for a version number in the main PHP file headerAffected if The installed version matches or falls within a vulnerable version range for this CVE
-
Identify plugin admin actions lacking noncesReview plugin source code (main PHP file) for form submissions and admin action hooks (admin_post_, wp_ajax_) - look for missing nonce verification calls like wp_verify_nonce or check_admin_refererAffected if State-changing operations (save/update actions) are found without anti-CSRF nonce checks
-
Inspect for stored XSS in plugin-generated contentView the plugin's public-facing pages or shortcodes on the site. View page source and search for any injected script tags or suspicious JavaScript in the HTMLAffected if Unexpected script tags or JavaScript code appears in the rendered output of plugin-generated pages
-
Check admin activity logs for suspicious plugin actionsReview WordPress audit logs, server access logs, or security plugins for POST requests to admin-post.php or wp-ajax.php actions related to the plugin with unusual parametersAffected if Requests to plugin admin actions are present from unexpected sources or contain XSS payloads in parameters
A user is affected if the MMX - Make Me Christmas plugin is installed and lacks anti-CSRF protections on admin actions, allowing stored XSS payloads to persist in plugin 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 dataImplement anti-CSRF tokens (nonces) for all state-changing operations and sanitize/validate all user inputs before storage and output.
- 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-2025-31401 — 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-31401 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