dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-25072

HIGH · 7.1 CVSS v3.1 Published 2025-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in thunderbax WP Admin Custom Page wp-admin-custom-page allows Stored XSS.This issue affects WP Admin Custom Page: from n/a through <= 1.5.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 confidence

This is a CSRF vulnerability in the WP Admin Custom Page WordPress plugin that allows Stored XSS. An attacker can craft a malicious link or form that, when clicked by a logged-in administrator, submits requests without the victim's consent, enabling injection of persistent malicious scripts into admin-customized pages.

MitigationUpdate to the latest version of WP Admin Custom Page when available, or disable the plugin until a patch is released. Implement anti-CSRF tokens (nonces) on all forms and AJAX actions within the plugin.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Admin Custom Page plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Admin Custom Page' or 'admin-custom-page' in the plugins directory.
    Affected if The plugin is not found in the installed plugins list, then you are not affected.
  2. Check the installed version of the plugin
    In the Plugins list, locate WP Admin Custom Page and read the version number displayed below the plugin name. Compare this version to the affected version range mentioned in CVE-2025-25072.
    Affected if Your installed version falls within the affected version range and the plugin is active.
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that WP Admin Custom Page shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is active and your version is within the affected range.
  4. Inspect if custom admin page functionality is in use
    Look for custom-created admin pages by checking the plugin's settings menu (often under Settings or a dedicated menu item created by the plugin) for any configured custom admin pages or modified admin interfaces.
    Affected if Custom admin pages have been created using the plugin, increasing the potential impact of stored XSS.
  5. Review plugin configuration for exposed settings
    Access the plugin settings page and check if any forms or AJAX actions are present without visible nonce token fields, or inspect page source for 'wpnonce' or '_wpnonce' parameters in plugin-generated forms.
    Affected if Forms or AJAX actions lack anti-CSRF nonce verification, indicating the vulnerability may be exploitable.

You are affected if WP Admin Custom Page is installed, active, within the vulnerable version range, and uses the custom admin page creation feature without CSRF protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of WP Admin Custom Page when available, or disable the plugin until a patch is released. Implement anti-CSRF tokens (nonces) on all forms and AJAX actions within the plugin.

Recommended fix Moderate confidence

Version 1.5.1 or later (verify latest version on WordPress plugin repository)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'WP Admin Custom Page' (thunderbax) plugin
  4. 4. Deactivate the plugin if an update is not immediately available
  5. 5. Check for available plugin updates or visit the WordPress plugin repository
  6. 6. If version 1.5.1 or later is available, update the plugin to the latest version
  7. 7. Verify the update was successful and the plugin is functioning correctly
Caveat Review plugin settings after update as configuration may need re-verification

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25072 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25072 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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