CVE-2024-49216
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 jclay06 Feed Comments Number feed-comments-number allows Upload a Web Shell to a Web Server.This issue affects Feed Comments Number: from n/a through <= 0.2.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 Feed Comments Number WordPress plugin (versions <= 0.2.1) contains an unrestricted file upload vulnerability that allows unauthenticated attackers to upload arbitrary files, including malicious PHP scripts (web shells), directly to the web server. This achieves remote code execution on the affected WordPress installation.
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.
-
Verify plugin presenceList the contents of the /wp-content/plugins/ directory and look for a folder related to feed comments, feed number, or similar functionality. Common naming may include 'feed-comments-number', 'fcn', or variations thereof.Affected if The plugin folder exists in /wp-content/plugins/ and its version is 0.2.1 or lower, or the version cannot be determined but the plugin is present.
-
Identify installed versionOpen the main plugin PHP file (usually the same name as the plugin folder, e.g., feed-comments-number.php) and look for a version comment or the 'Version' header in the plugin metadata at the top of the file. Compare this version to the affected range of <= 0.2.1.Affected if The plugin version listed in the plugin header is 0.2.1 or lower, or no version is declared but the plugin is installed.
-
Inspect upload directoriesCheck the /wp-content/uploads/ directory (and any dated subdirectories within it) for unexpected .php files, .php.txt files, or other suspicious file extensions that were not intentionally uploaded through WordPress media functions.Affected if Unexpected PHP files exist in the uploads directory that were not deliberately added by an administrator.
-
Review access logsExamine the web server access logs (typically in /var/log/nginx/ or /var/log/apache2/) for POST requests to the plugin's upload endpoint. Look for patterns like 'wp-content/plugins/feed-comments-number/*' with file upload activity from unauthenticated sources.Affected if POST requests to the plugin's file upload functionality appear in the logs from IP addresses that should not have upload privileges.
If the Feed Comments Number plugin is installed and its version is 0.2.1 or lower, or if unexpected PHP files exist in the uploads directory, the environment is likely affected.
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 to the latest version of the Feed Comments Number plugin immediately. If no patched version exists, remove the plugin entirely and audit the server for any already-uploaded web shells or backdoors.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49216 — 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-49216 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