CVE-2025-29009
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 Webkul Medical Prescription Attachment Plugin for WooCommerce medical-prescription-attachment-plugin-for-woocommerce allows Upload a Web Shell to a Web Server.This issue affects Medical Prescription Attachment Plugin for WooCommerce: from n/a through <= 1.2.3.
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 confidenceUnrestricted file upload vulnerability in Webkul Medical Prescription Attachment Plugin for WooCommerce allows unauthenticated attackers to upload dangerous file types, including web shells, directly to the web server. This provides attackers with remote code execution capabilities and full control over the affected WordPress 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.
-
Confirm plugin installationCheck your WordPress site's wp-content/plugins/ directory for a folder named 'medical-prescription' or similar, or list all installed WooCommerce plugins via WordPress admin or wp-cli: wp plugin list --status=activeAffected if The Webkul Medical Prescription Attachment Plugin is present and active in the WordPress/WooCommerce installation
-
Identify plugin versionAccess the plugin file header (e.g., medical-prescription/medical-prescription.php) and locate the 'Version' comment, or view the version in WordPress admin under Plugins > Installed PluginsAffected if The installed version matches or falls within any affected version range for this CVE
-
Verify upload functionality is accessibleCheck if the medical prescription upload form/endpoint is publicly accessible by reviewing the plugin's routing or by attempting to access any upload-related pages exposed by the pluginAffected if The upload endpoint is accessible to unauthenticated users (this plugin allows unauthenticated uploads)
-
Inspect upload storage locationExamine the plugin settings or code to determine the directory where uploaded files are stored (typically wp-content/uploads/ or a plugin-specific subdirectory); use grep to search for upload_dir or move_uploaded_file in plugin filesAffected if Uploaded files are stored within the webroot (wp-content or similar web-accessible directory)
-
Check file execution restrictionsReview the web server configuration (Apache .htaccess, Nginx config) and the upload directory for restrictions preventing PHP execution; verify that .php files in the upload folder cannot be executed via browserAffected if Uploaded PHP files can be executed by requesting them directly through the web server (no execution prevention in place)
If the Webkul Medical Prescription Attachment Plugin is installed, the upload feature is accessible to visitors, and uploaded files are stored in a web-accessible directory without execution restrictions, the environment is vulnerable to remote code execution via this CVE.
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 dataUpgrade the Medical Prescription Attachment Plugin for WooCommerce to the latest version immediately. If no patched version is available, remove the plugin until a fix is released.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29009 — 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-29009 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