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

CVE-2025-57977

HIGH · 7.1 CVSS v3.1 Published 2025-09-22
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 wpdesk Flexible PDF Invoices for WooCommerce & WordPress flexible-invoices allows Cross Site Request Forgery.This issue affects Flexible PDF Invoices for WooCommerce & WordPress: from n/a through <= 6.0.13.

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 flexible-invoices plugin allows attackers to trick authenticated administrators into unknowingly performing unintended actions (such as modifying invoice settings or generating PDFs) via maliciously crafted requests. The lack of anti-CSRF tokens on state-changing operations enables attackers to exploit the trusted relationship between the user's browser and the vulnerable WordPress site.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations (forms, AJAX endpoints, admin actions) and validate these tokens server-side. Additionally, set SameSite=Strict or SameSite=Lax attributes on session cookies.

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H

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. Locate the flexible-invoices plugin version
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and find flexible-invoices. The version number is displayed beneath the plugin name. Alternatively, check the plugin header in its main PHP file (typically in /wp-content/plugins/flexible-invoices/ or similar path) or the readme.txt file.
    Affected if The installed version falls within the affected version range for this CVE (compare your version to the officially published vulnerable versions).
  2. Identify state-changing operations in the plugin
    Review the plugin source code for functions that modify data or trigger actions, such as: invoice settings updates, PDF generation endpoints, invoice creation/modification, and any admin action handlers. Look for form handlers and AJAX endpoints in the plugin's PHP files.
    Affected if The plugin handles administrator actions (settings changes, PDF generation, invoice modifications) without requiring the user to explicitly confirm the action.
  3. Inspect forms for anti-CSRF nonce fields
    Examine the plugin's PHP files that render forms (especially in admin settings pages and frontend invoice forms). Search for calls to wp_nonce_field(), wp_nonce_url(), or check_admin_referer(). Verify that these nonce fields are present in all forms that perform state-changing operations.
    Affected if Forms that submit state-changing requests (settings updates, PDF generation, invoice actions) lack nonce token fields or do not validate nonces server-side.
  4. Check AJAX endpoints for nonce verification
    Inspect the plugin's AJAX handlers (look for wp_ajax_ and wp_ajax_nopriv_ hooks). Verify that each handler includes a nonce check using check_ajax_referer() or wp_verify_nonce() before processing the request.
    Affected if AJAX endpoints that handle state-changing operations do not verify nonce tokens, allowing requests to be forged from malicious sites.
  5. Review session cookie SameSite attribute
    Inspect the WordPress session cookie configuration. In a staging environment, log into the admin and examine the Set-Cookie headers (via browser dev tools or a proxy). Verify if the WordPress session cookie has a SameSite attribute set to Strict or Lax.
    Affected if The session cookie lacks a SameSite attribute or is set to SameSite=None, which can facilitate CSRF attacks.

A user is affected if the flexible-invoices plugin version is within the vulnerable range AND the plugin's state-changing operations (forms, AJAX endpoints) lack proper anti-CSRF nonce validation.

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 (nonces) on all state-changing operations (forms, AJAX endpoints, admin actions) and validate these tokens server-side. Additionally, set SameSite=Strict or SameSite=Lax attributes on session cookies.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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