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

CVE-2025-10268

CVE-2025-10268 Path Traversal in Printcart
📅 PUBLISHED: 2026-06-26 06:00 UTC 🔄 UPDATED: 2026-08-12 14:52 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.16%
👁️
0.16% probability
3.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.
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 0.0
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: N User Interaction None
S: U Scope Unchanged
C: L Confidentiality Low
I: N Integrity None
A: N Availability None
SOON
PENDING NVD
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-10268 is a Path Traversal vulnerability affecting the Printcart Web to Print Product Designer for WooCommerce WordPress plugin, versions up to and including 2.4.8. This vulnerability allows an unauthenticated attacker to retrieve directory listings of arbitrary directories on the server, leading to information disclosure. The vulnerability is classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory). No official patch has been released by the vendor at this time.

⚡ 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 within the WordPress plugin ecosystem. The plugin is distributed via the official WordPress plugin repository and is installed as a standard WordPress plugin. Users are advised to monitor the plugin's page for updates and consider removing the plugin if no patch is forthcoming.

CVSS Breakdown & Threat Level

  • CVSS Score: 0.0 (Base Score not provided by NVD, but based on vector: 5.3 Medium)
  • Attack Vector (AV): Network (N)
  • Attack Complexity (AC): Low (L)
  • Privileges Required (PR): None (N)
  • User Interaction (UI): None (N)
  • Scope (S): Unchanged (U)
  • Confidentiality (C): Low (L)
  • Integrity (I): None (N)
  • Availability (A): None (N)

Threat Level: Medium. The vulnerability allows an attacker to enumerate directory structures and potentially discover sensitive files, but does not directly lead to code execution or data modification.

Deep Dive & Mechanics

The vulnerability exists due to insufficient sanitization of user-supplied input when handling directory listing requests. The plugin likely uses a parameter (e.g., dir, path, or folder) to specify which directory to list. Without proper validation, an attacker can inject path traversal sequences (e.g., ../) to navigate outside the intended web root.

Root Cause: The plugin fails to validate or sanitize the directory path parameter, allowing traversal to arbitrary directories.

Attack Vector: An unauthenticated attacker sends a crafted HTTP request to the vulnerable endpoint, manipulating the directory parameter to traverse the filesystem.

Impact: Successful exploitation reveals the directory listing of arbitrary directories, potentially exposing sensitive files such as configuration files, logs, or other plugins' data.

Vulnerable vs. Patched Code

Since no official patch is available, the following is a hypothetical example of the vulnerable code and a potential fix.

Vulnerable Code (PHP):

<?php
$dir = $_GET['dir'];
$files = scandir($dir);
foreach ($files as $file) {
    echo $file . "\n";
}
?>

Patched Code (PHP):

<?php
$dir = $_GET['dir'];
$base_dir = '/var/www/html/wp-content/uploads/printcart/';
$real_path = realpath($base_dir . $dir);
if (strpos($real_path, $base_dir) !== 0) {
    die('Invalid path.');
}
$files = scandir($real_path);
foreach ($files as $file) {
    echo $file . "\n";
}
?>

Exploitation & Lab Setup

Red Team

Prerequisites:

  • A WordPress installation with the Printcart plugin (version <= 2.4.8) active.
  • The vulnerable endpoint is typically /wp-admin/admin-ajax.php or a custom endpoint.

Exploitation Steps:

  1. Identify the vulnerable parameter (e.g., dir, path, folder).
  2. Send a GET request with path traversal sequences:
    curl "http://target.com/wp-content/plugins/printcart/ajax.php?dir=../../../etc"
    
  3. Observe the directory listing of /etc or other sensitive directories.

Example Request:

GET /wp-content/plugins/printcart/ajax.php?dir=../../../etc HTTP/1.1
Host: target.com

Blue Team

Detection:

  • Monitor for requests containing ../ or ..%2f in parameters related to directory listing.
  • Look for unusual directory traversal patterns in web server logs.

Mitigation:

  • Implement input validation and sanitization for all directory parameters.
  • Use a whitelist of allowed directories.
  • Apply the principle of least privilege to the web server user.

Indicators of Compromise (IOCs)

  • Network IOCs:
    • HTTP requests with path traversal sequences in the dir parameter.
    • Unusual directory listing responses (e.g., listing of /etc, /var/log).
  • File System IOCs:
    • Unexpected directory listing outputs in web server logs.
  • Log IOCs:
    • Web server logs showing requests to /wp-content/plugins/printcart/ajax.php with ../ patterns.

Detection Engineering

YARA Rule

rule CVE_2025_10268_Printcart_Path_Traversal {
    meta:
        description = "Detects path traversal attempts against Printcart plugin"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2025-10268"
    strings:
        $traversal1 = "../"
        $traversal2 = "..\\"
        $traversal3 = "%2e%2e%2f"
        $traversal4 = "%2e%2e/"
        $plugin_path = "/wp-content/plugins/printcart/"
    condition:
        any of ($traversal*) and $plugin_path
}

Sigma Rule

title: Printcart Path Traversal Attempt
id: 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d
status: experimental
description: Detects path traversal attempts against Printcart plugin
author: Valters IT
date: 2025/04/10
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-uri-query|contains:
            - '../'
            - '..%2f'
            - '%2e%2e%2f'
        cs-uri-stem|contains: '/wp-content/plugins/printcart/'
    condition: selection
falsepositives:
    - Legitimate use of '..' in filenames (rare)
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2025-10268 Printcart Path Traversal Attempt"; flow:to_server,established; content:"/wp-content/plugins/printcart/"; http_uri; content:"../"; http_uri; distance:0; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Disable the plugin until a patch is available.
  2. Implement a Web Application Firewall (WAF) rule to block path traversal patterns.
  3. Restrict directory listing via server configuration (e.g., disable Options +Indexes in Apache).

Long-term Fix:

  • The vendor must release a patched version that properly validates and sanitizes directory parameters.
  • Users should update to the latest version once available.

Workarounds:

  • Use a reverse proxy to filter out malicious requests.
  • Apply virtual patching via WAF.

Valters IT

👁️ 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.title:"Printcart"
http.html:"printcart"
wp-content/plugins/printcart/

💣 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-10268/ · 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.