CVE-2025-30981
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 tggfref WP-Recall allows Privilege Escalation. This issue affects WP-Recall: from n/a through 16.26.14.
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 confidenceCSRF vulnerability in the WP-Recall WordPress plugin allows authenticated attackers to perform privilege escalation by tricking authenticated users (including administrators) into executing unwanted actions through forged HTTP requests. The vulnerability exists in versions up to 16.26.14.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 WP-Recall plugin is installedCheck the WordPress plugins directory or use wp plugin list to confirm WP-Recall is present in the installationAffected if WP-Recall is installed and active in the WordPress environment
-
Check installed version against affected rangeRetrieve the installed version number of WP-Recall (via plugin admin page, wp-cli, or version constant in plugin main file) and compare it to the affected range: any version up to and including 16.26.14Affected if The installed version is 16.26.14 or lower
-
Confirm plugin is activeVerify the plugin status is 'Active' in WordPress admin under Plugins or via wp plugin statusAffected if The plugin is activated and accessible to authenticated users
-
Identify vulnerable state-changing endpointsReview plugin PHP files for AJAX handlers (wp_ajax_* hooks) and form processing logic that modify user data, roles, or settings without nonce verificationAffected if The plugin contains AJAX endpoints or forms that handle privilege-related actions without CSRF token validation
-
Check for nonce implementation gapsSearch plugin source code for presence of wp_verify_nonce, check_ajax_referer, or nonces in form fields; look for missing implementations in sensitive function handlersAffected if State-changing actions lack proper nonce validation and are reachable via forged requests from authenticated users
The environment is affected if WP-Recall version 16.26.14 or lower is installed and active with AJAX endpoints or forms lacking CSRF protection for privilege-escalating actions.
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 forms and AJAX endpoints, validate request origin/referer headers, and add SameSite cookie attributes to session cookies.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30981 — 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-30981 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