CVE-2025-60235
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Plugify Support Ticket System for WooCommerce (Premium) support-ticket-system-for-woocommerce allows Using Malicious Files.This issue affects Support Ticket System for WooCommerce (Premium): from n/a through <= 2.0.7.
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 confidenceThis is an unrestricted file upload vulnerability in the Plugify Support Ticket System for WooCommerce Premium plugin (versions up to 2.0.7). The plugin fails to properly validate uploaded file types, allowing attackers to upload malicious files (such as PHP scripts or web shells) that could lead to remote code execution on the affected WordPress/WooCommerce site.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Identify if Plugify Support Ticket System for WooCommerce (Premium) plugin is installedAccess your WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Plugify Support Ticket System' or 'Support Ticket System for WooCommerce'. Alternatively, check the /wp-content/plugins/ directory for a plugin folder containing 'plugify' and 'support-ticket' in the name.Affected if The plugin is present in the WordPress installation
-
Determine the installed version of the pluginIn the WordPress admin Plugins list, find the Plugify Support Ticket System entry and locate the version number displayed beneath the plugin name. If not visible in the admin, inspect the main plugin PHP file and look for a 'Version' header in the plugin comments.Affected if The version number is 2.0.7 or lower, or any version up to and including 2.0.7
-
Verify the support ticket file upload feature is accessibleLog in as a customer or create a test support ticket through the WooCommerce account. Navigate to the ticket creation or reply interface and check if a file upload field (typically labeled 'Attachment', 'Upload File', or similar) is present and functional.Affected if The file upload form field is present and operational on the support ticket submission page
-
Inspect uploaded file storage locationCheck the wp-content/uploads/ directory (or custom upload directory configured in WordPress) for subfolders related to support tickets. Verify whether uploaded files are stored in a location accessible via web browser and if PHP execution restrictions are in place.Affected if Uploaded files are stored within the web-accessible directory without PHP execution disabled
You are affected if the Plugify Support Ticket System for WooCommerce (Premium) plugin is installed with version 2.0.7 or lower and the support ticket upload feature is accessible to users.
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 dataImmediately restrict or disable file upload functionality until a patched version is available; implement strict allowlist-based file type validation, store uploads outside the web root, and disable script execution in upload directories.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60235 — 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-60235 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