Plugin PropagatorWordPress extension · Widgilabs
CVE-2024-50495
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 nunomorgadinho Plugin Propagator wp-propagator allows Upload a Web Shell to a Web Server.This issue affects Plugin Propagator: from n/a through <= 0.1.
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 wp-propagator WordPress plugin from nunomorgadinho contains an unrestricted file upload vulnerability allowing attackers to upload dangerous file types (web shells) directly to the web server, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Plugin PropagatorWordPress extension
<= 0.1CVSS 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.
-
Identify if wp-propagator plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-propagator', 'plugin-propagator', or similar variants from nunomorgadinho or WidgilabsAffected if The plugin directory exists on the server
-
Determine the installed plugin versionOpen the main plugin PHP file and look for the version string in the plugin header comment (e.g., 'Version: x.x')Affected if The version is 0.1 or lower, or if no version is displayed (which may indicate an unversioned copy of the vulnerable release)
-
Inspect the plugin upload functionalityIf the plugin is present, locate the file upload handling code within the plugin directory - look for PHP files containing 'upload', 'file', or 'POST' handling logicAffected if The plugin contains any file upload processing code that accepts user-supplied files without restriction
-
Check the uploads directory for suspicious filesExamine wp-content/uploads/ (or custom upload directory) for recently created files with dangerous extensions such as .php, .phtml, .php5, .phar, or .jpg.phpAffected if Any unknown PHP or executable files exist in upload directories, especially if created recently or with obfuscated names
-
Review access logs for upload endpoint requestsSearch web server access logs (Apache/nginx) for POST requests to the plugin's upload handler URL, looking for attempts to upload file types like .phpAffected if Logs show POST requests to the plugin uploading files with executable extensions
You are affected if the wp-propagator plugin from nunomorgadinho is installed at version 0.1 or lower, as this version contains the unrestricted file upload vulnerability that allows remote attackers to upload web shells.
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 dataDisable or remove the affected plugin until a patched version is available; if a patch is released, update immediately and review uploaded files directory for existing malicious payloads.
Fix this in Plugin Propagator
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50495 — 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-2024-50495 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