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

CVE-2025-22301

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-07
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 zookatron MyBookTable Bookstore mybooktable allows Cross Site Request Forgery.This issue affects MyBookTable Bookstore: from n/a through <= 3.5.3.

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

A Cross-Site Request Forgery (CSRF) vulnerability exists in MyBookTable Bookstore plugin versions 3.5.3 and below. The flaw allows attackers to trick authenticated users into unknowingly submitting malicious requests to the application, potentially leading to unauthorized actions such as modifying book data or user settings. The medium severity (CVSS 5.4) indicates the attack requires user interaction and results in partial integrity impact.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing forms and validate them server-side, along with enforcing SameSite cookie attributes and verifying Origin/Referer headers to prevent cross-origin 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 MyBookTable plugin installation and version
    Locate the MyBookTable plugin directory (typically in wp-content/plugins/mybooktable or similar) and open the main plugin file (e.g., mybooktable.php) to read the version header declared in the plugin metadata
    Affected if The version listed is 3.5.3 or lower (e.g., 3.5.3, 3.5.2, 3.5.1, 3.5.0, or any version below 3.5.3)
  2. Identify state-changing forms in the plugin
    Access the plugin admin interface and locate forms that modify data, such as the Add Book form, Edit Book form, and User Settings form. View the page source (HTML) of these forms to inspect the form markup
    Affected if Forms that submit data to the server (POST requests that add, edit, or delete book entries or modify user settings) exist in the plugin
  3. Inspect forms for CSRF protection tokens
    In the HTML source of each state-changing form, search for hidden input fields containing tokens (commonly named nonce, csrftoken, _wpnonce, or similar) or examine if the form submits to an endpoint that validates such tokens
    Affected if No hidden CSRF token field is present in the form, or the form action does not reference a server-side nonce validation mechanism
  4. Verify cookie security attributes
    Log into the WordPress admin area where MyBookTable is active, open browser developer tools (Application tab > Cookies), and examine the authentication cookies set for the domain
    Affected if Cookies lack the SameSite attribute or have SameSite set to None without the Secure flag, making them vulnerable to cross-origin CSRF attacks
  5. Check server-side request origin validation
    Intercept a legitimate form submission using a proxy or browser dev tools and examine if the server rejects requests with missing or mismatched Origin or Referer headers, or check server logs for such validation behavior
    Affected if The server accepts and processes form submissions without validating that the Origin or Referer header matches the expected domain

A user is affected if MyBookTable plugin version 3.5.3 or lower is installed AND state-changing forms lack CSRF tokens or proper SameSite cookie attributes, allowing cross-origin malicious requests to succeed.

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 anti-CSRF tokens (synchronizer token pattern) on all state-changing forms and validate them server-side, along with enforcing SameSite cookie attributes and verifying Origin/Referer headers to prevent cross-origin requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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