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

CVE-2025-31448

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 misteraon Simple Trackback Disabler simple-trackback-disabler allows Cross Site Request Forgery.This issue affects Simple Trackback Disabler: from n/a through <= 1.4.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Simple Trackback Disabler WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (such as enabling/disabling trackbacks) by exploiting the lack of anti-CSRF token validation on state-changing requests.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that modify plugin settings, and verify the nonce on the server-side before processing any state-changing requests.

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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. Confirm plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Simple Trackback Disabler' in the list. Note whether it is activated.
    Affected if The plugin is installed and activated, exposing the admin interface to potential CSRF attacks.
  2. Identify installed plugin version
    Click on the plugin name in the Plugins list to view its details, or inspect the plugin's main PHP file header for the 'Version' comment tag.
    Affected if The installed version matches any version known to lack anti-CSRF protection on state-changing requests.
  3. Inspect admin settings forms for nonce fields
    Access the plugin settings page (usually under Settings > Simple Trackback Disabler or similar). View the page source (right-click > View Page Source) and search for input fields with 'nonce' in the name attribute. Check if the forms that enable/disable trackbacks include a wpnonce or _wpnonce hidden field.
    Affected if The settings forms that toggle trackback state do not contain a WordPress nonce field, indicating missing CSRF protection.
  4. Verify nonce validation in plugin PHP code
    Locate the plugin directory (wp-content/plugins/simple-trackback-disabler or similar). Open the main PHP file and search for functions that handle the enable/disable trackback actions. Look for calls to wp_verify_nonce, check_admin_referer, or verify_nonce before processing the request.
    Affected if The state-changing functions lack server-side nonce verification, meaning the plugin does not validate that the request originated from a legitimate admin session.
  5. Test AJAX actions for CSRF protection
    If the plugin uses AJAX to change trackback settings, examine the JavaScript files or inline scripts. Check if AJAX requests include a nonce parameter (such as _wpnonce or security) in the request data.
    Affected if AJAX actions that modify trackback settings do not send or validate a nonce token, allowing attackers to forge requests.

You are affected if the Simple Trackback Disabler plugin is installed and its code lacks WordPress nonce verification on forms or AJAX actions that change trackback settings.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions that modify plugin settings, and verify the nonce on the server-side before processing any state-changing requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31448 — 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-31448 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