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

CVE-2025-49239

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-06
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 tychesoftwares Print Invoice & Delivery Notes for WooCommerce woocommerce-delivery-notes allows Cross Site Request Forgery.This issue affects Print Invoice & Delivery Notes for WooCommerce: from n/a through <= 5.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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Print Invoice & Delivery Notes for WooCommerce plugin allows remote attackers to trick authenticated administrators into performing unintended actions via malicious crafted requests, likely due to missing or improper anti-CSRF token validation on sensitive plugin actions.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX actions within the plugin, and verify the nonce validity 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. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Print Invoice & Delivery Notes for WooCommerce and note the version number displayed, or check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The installed version matches any affected version range (compare to official WordPress plugin repository for patch status)
  2. Inspect plugin forms for nonce fields
    Navigate to WooCommerce > Settings > Print Invoice (or any plugin admin pages), view the page source (right-click > View Page Source) and search for 'wpnonce' or '_wp_nonce' hidden input fields within <form> tags
    Affected if No nonce fields are present in admin forms, or nonces are present but not validated server-side (requires code review of form handlers)
  3. Check AJAX handlers for nonce verification
    Examine the plugin's PHP files for AJAX action callbacks (search for 'add_action("wp_ajax_' ) and verify if wp_verify_nonce() or check_admin_referer() is called before processing requests
    Affected if AJAX actions process requests without verifying nonce tokens server-side
  4. Review admin action handlers for nonce validation
    Search the plugin PHP files for admin action hooks (like 'admin_init' or custom action parameters) and check if nonce verification occurs before any state-changing operations (database writes, settings updates, etc.)
    Affected if Admin actions execute without prior nonce validation allowing forged requests

You are affected if the installed plugin version has not been patched AND the plugin lacks proper WordPress nonce validation on its forms, AJAX endpoints, or admin action handlers.

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

Implement WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX actions within the plugin, and verify the nonce validity server-side before processing any state-changing requests.

Recommended fix Moderate confidence

Version higher than 5.5.0 (any version released after 5.5.0 containing the security fix)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Print Invoice & Delivery Notes for WooCommerce' by tychesoftwares
  4. Check the current version is 5.5.0 or below
  5. Click 'Update now' if an update is available, or manually download a version newer than 5.5.0 from the WordPress plugin repository
  6. Verify the plugin updated successfully to a version above 5.5.0

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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