AffiliatorWordPress extension · Vasiliskerasiotis
CVE-2024-49326
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 Vasileios Kerasiotis Affiliator affiliator-lite allows Upload a Web Shell to a Web Server.This issue affects Affiliator: from n/a through <= 2.1.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 confidenceThe Affiliator plugin for WordPress (versions up to 2.1.3) contains an unrestricted file upload vulnerability allowing remote attackers to upload malicious PHP files (web shells) directly to the web server without proper validation of file types or contents, leading to potential complete 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
AffiliatorWordPress extension
<= 2.1.3CVSS 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 Affiliator plugin is installedCheck your WordPress plugins directory for a folder named 'affiliator' or search your site for files containing 'Affiliator' plugin headersAffected if The Affiliator plugin by Vasiliskerasiotis is found in your plugins directory
-
Verify the installed versionCheck the main plugin file (typically affiliator.php) for the 'Version' header in the plugin comments, or query the WordPress plugins APIAffected if The reported version is 2.1.3 or lower
-
Inspect upload directories for unexpected PHP filesSearch your wp-content/uploads folder (and any custom upload directories) for .php files, especially those created recently or with randomized namesAffected if Unexpected or unknown PHP files exist in upload directories
-
Review access logs for upload endpoint abuseSearch web server access logs for POST requests to the plugin's upload functionality (look for uris containing 'affiliator' and 'upload' or similar) from unauthenticated sourcesAffected if Unauthenticated POST requests to upload endpoints are found in logs
-
Check webroot for newly created PHP filesPerform a filesystem scan for recently created .php files in publicly accessible web directories, particularly outside standard plugin/theme locationsAffected if Unknown PHP files with suspicious content exist in web-accessible directories
You are affected if the Affiliator plugin version is 2.1.3 or lower and the upload feature is accessible to unauthenticated users, or if suspicious PHP files are found in upload or web directories.
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 remove or disable the vulnerable plugin version; implement strict allowlist-based file type validation server-side (checking magic bytes not just extensions), enforce authentication for upload endpoints, and move uploaded files outside webroot.
Fix this in Affiliator
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49326 — 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-49326 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