CVE-2025-46457
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 Ahsanullah Akanda Wp Custom CMS Block wp-custom-cms-block allows Stored XSS.This issue affects Wp Custom CMS Block: from n/a through <= 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 · moderate confidenceA CSRF vulnerability in the Wp Custom CMS Block WordPress plugin (versions up to 2.1) allows attackers to trick authenticated administrators into submitting malicious requests that inject and store XSS payloads into CMS blocks. The stored XSS executes when other users view the compromised 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.
-
Confirm plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Wp Custom CMS Block'. Note the installed version number. Alternatively, check the plugin header in /wp-content/plugins/wp-custom-cms-block/ folder.Affected if The plugin is installed and the version is 2.1 or lower.
-
Verify nonce token presence in admin formsInspect the source code of the plugin's admin pages (block creation/editing forms). Look for wp_nonce_field() or wp_nonce_url() function calls within the form definitions. Check both the main admin page and any AJAX handlers used by the plugin.Affected if The plugin's admin forms and AJAX actions lack nonce verification (wp_nonce_field or similar is missing or not properly validated).
-
Inspect CMS blocks for stored XSSAccess the plugin's CMS block management interface. Review all existing blocks for any suspicious content such as <script> tags, javascript: URLs, event handlers (onload, onerror, onmouseover), or encoded payloads that may indicate XSS injection.Affected if Any CMS blocks contain unescaped HTML, script tags, or known XSS payload patterns.
-
Check user session isolationCreate a secondary administrator or editor account. Log in with that account and navigate to pages that display CMS blocks created by the first account. Observe whether any injected scripts execute in the second session.Affected if Injected JavaScript or HTML executes when viewing CMS blocks as a different user than the one who created them.
A user is affected if the Wp Custom CMS Block plugin version 2.1 or lower is installed and the plugin lacks proper nonce validation on admin forms, allowing stored XSS payloads to persist and execute for other users.
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 admin-side forms and AJAX actions, and apply proper input sanitization and output escaping to prevent stored XSS.
- 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-46457 — 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-46457 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