CVE-2025-23430
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 Oren Yomtov Mass Custom Fields Manager mass-custom-fields-manager allows Reflected XSS.This issue affects Mass Custom Fields Manager: from n/a through <= 1.5.
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 Mass Custom Fields Manager plugin enables attackers to craft malicious requests that, when triggered by an authenticated administrator, result in Reflected XSS. The lack of proper CSRF token validation on form actions allows attackers to inject arbitrary JavaScript through crafted links or embedded forms.
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 Mass Custom Fields Manager plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the mass-custom-fields-manager folderAffected if The plugin is installed and active
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Mass Custom Fields Manager and note the version number displayed, or check the plugin's main PHP file for the 'Version' header in the plugin commentsAffected if The version cannot be confirmed as patched or is within an affected range (if known)
-
Inspect form actions for CSRF token presenceView page source of the plugin's admin pages containing forms (especially settings or field management forms). Look for input fields with names like 'nonce', '_wpnonce', 'security', or similar token fields. Check if forms submit to admin-post.php or custom AJAX handlers.Affected if Forms lack CSRF token (nonce) input fields or the tokens are not validated server-side
-
Verify admin session is activeConfirm you are logged into WordPress as an administrator user with access to the Mass Custom Fields Manager plugin settingsAffected if An authenticated administrator session exists (required for the CSRF attack to execute)
-
Test for reflected XSS in form submissionsSubmit a test form with a benign payload like '<script>alert(1)</script>' in a custom field name or value parameter. If the input is reflected back without encoding in the response, the XSS vector exists.Affected if User-supplied input is reflected unescaped in the plugin's response pages
If the Mass Custom Fields Manager plugin is active, forms lack CSRF tokens, and the plugin reflects user input without encoding, then the environment is vulnerable to CVE-2025-23430.
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) on all state-changing actions and properly encode output to prevent reflected 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-2025-23430 — 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-23430 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