dbcve.org
Woocommerce Pdf Invoice BuilderWordPress extension · Rednao

CVE-2023-51486

HIGH · 8.8 CVSS v3.1 Published 2024-03-16
Fix available
A fix is available. Upgrade to 1.2.102 or later.
See remediation →
95/100
Remediation priority · Urgent
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 RedNao WooCommerce PDF Invoice Builder.This issue affects WooCommerce PDF Invoice Builder: from n/a through 1.2.101.

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 RedNao WooCommerce PDF Invoice Builder plugin allows attackers to perform unauthorized actions on behalf of authenticated users by tricking them into visiting malicious pages while logged in. The plugin lacks proper CSRF token validation on state-changing operations.

MitigationImplement anti-CSRF tokens (nonces) on all forms and AJAX endpoints that perform state-changing operations, validate tokens server-side, and add SameSite attributes to session cookies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce Pdf Invoice BuilderWordPress extension
Affected:< 1.2.102

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 plugin installation
    Access your WordPress site's wp-content/plugins/ directory and search for a folder named 'woo-pdf-invoice-builder' or similar. Check the main plugin file (usually named main.php, plugin.php, or index.php) to find the plugin header which contains the version number.
    Affected if The plugin is installed and the version is below 1.2.102
  2. Verify the installed version
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Rednao WooCommerce PDF Invoice Builder' to confirm its reported version number.
    Affected if The displayed version is less than 1.2.102
  3. Inspect plugin for CSRF token implementation
    Access the plugin source code via FTP or file manager. Search the PHP files for 'wp_nonce', 'wp_create_nonce', 'verify_nonce', or 'check_admin_referer' which are WordPress nonce functions used for CSRF protection.
    Affected if State-changing functions (form submissions, AJAX endpoints) lack nonce verification calls
  4. Check AJAX endpoints for CSRF protection
    Search the plugin files for 'add_action' calls registering AJAX handlers (like 'wp_ajax_'). Examine each handler to see if it calls 'check_ajax_referer' or 'wp_verify_nonce' before processing the request.
    Affected if AJAX endpoints performing state changes do not validate nonces
  5. Review cookie settings for SameSite attribute
    Examine the plugin code for 'setcookie' or 'session_start' calls. Check if the SameSite attribute is set to 'Strict' or 'Lax' on any session or authentication cookies the plugin creates.
    Affected if Cookies related to the plugin lack SameSite attributes

You are affected if the RedNao WooCommerce PDF Invoice Builder plugin is installed with a version number lower than 1.2.102 and the plugin code lacks nonce validation on its forms and AJAX endpoints.

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
Upgrade available Upgrade to 1.2.102 or later
Fixed in 1.2.102
Interim mitigation

Implement anti-CSRF tokens (nonces) on all forms and AJAX endpoints that perform state-changing operations, validate tokens server-side, and add SameSite attributes to session cookies.

Recommended fix High confidence

1.2.102

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WooCommerce PDF Invoice Builder' (RedNao) plugin
  4. Click 'Update now' if an update is available, or manually download version 1.2.102 from the WordPress plugin repository and upload it
  5. Verify the plugin is running version 1.2.102 or later after updating

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

Fix this in Woocommerce Pdf Invoice Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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