CVE-2025-4564
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 · uneditedThe TicketBAI Facturas para WooCommerce plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation via the 'delpdf' action in all versions up to, and including, 3.18. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
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 · high confidenceThe TicketBAI Facturas para WooCommerce WordPress plugin versions up to 3.18 contains an arbitrary file deletion vulnerability in the 'delpdf' action. The plugin fails to validate file paths properly, allowing unauthenticated attackers to delete any file on the server by manipulating the file path parameter. Deletion of critical files like wp-config.php can completely compromise the WordPress installation and enable remote code execution.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation and versionNavigate to WordPress admin > Plugins and locate TicketBAI Facturas para WooCommerce. Check the version number displayed. Alternatively, inspect the plugin main file header in wp-content/plugins/ticketbai-facturas-para-woocommerce/ticketbai.php for the 'Version' tag.Affected if The plugin version is 3.18 or lower (any version up to and including 3.18 is affected)
-
Confirm plugin is activeIn WordPress admin > Plugins, verify if TicketBAI Facturas para WooCommerce is currently activated. The vulnerability is exploitable when the plugin is active.Affected if The plugin is installed and active in WordPress, and version is 3.18 or below
-
Verify wp-config.php integrityCheck if the file wp-config.php exists in the WordPress root directory. Use an FTP client, file manager, or run 'ls -la wp-config.php' via command line.Affected if wp-config.php is missing or has been deleted - this indicates possible exploitation
-
Review server access logs for delpdf requestsExamine server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests containing 'delpdf' action in the query parameters or POST data. Search for patterns like 'action=delpdf' or '?action=delpdf'.Affected if Suspicious requests with the delpdf action are present, especially with manipulated file paths like '../../wp-config.php' or absolute paths to critical files
You are affected if the TicketBAI Facturas para WooCommerce plugin version is 3.18 or lower AND the plugin is active, or if evidence of delpdf exploitation appears in logs or critical files like wp-config.php are missing.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest version immediately. If wp-config.php was deleted, restore it from backup to recover the site. Consider reviewing server access logs for the 'delpdf' action to determine if the vulnerability was exploited.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4564 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4564 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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