PhotokitWordPress extension · Jackzhu
CVE-2024-49610
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 photokiteditor photokit photokit allows Upload a Web Shell to a Web Server.This issue affects photokit: from n/a through <= 1.0.
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 confidenceThe photokiteditor application contains an unrestricted file upload vulnerability in its upload functionality that lacks proper file type validation. This allows unauthenticated attackers to upload dangerous file types (such as PHP web shells) that can be executed on the server to achieve 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
PhotokitWordPress extension
<= 1.0CVSS 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.
-
Confirm photokit installationLocate photokit application files - look for directories or components named 'photokit' or 'PhotoKit' in your web server document root or application installation directoryAffected if photokit files are present in the web server environment
-
Determine installed versionCheck version metadata in application files (such as version.php, package.json, or a config file) and compare to the affected range of <= 1.0Affected if version is 1.0 or lower
-
Identify file upload functionalityLocate the upload handler/script in the photokit application - typically found in paths like /upload, /api/upload, or similar endpoints that process file uploadsAffected if file upload endpoint exists and is accessible via the web
-
Inspect file validation logicExamine the upload handling code for any file type, extension, or content-type validation checks before files are savedAffected if no file type validation is performed, or validation relies solely on client-side checks or file extension matching without content verification
-
Check upload directory locationIdentify where uploaded files are stored - check the upload path configuration in the application code and verify if it resides within the web-accessible document rootAffected if uploaded files are stored in a web-accessible directory and can be directly accessed via URL
A user is affected if photokit version 1.0 or lower is installed, contains an accessible file upload feature, and stores uploaded files in a web-accessible location without proper server-side file type validation.
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 dataImplement strict allowlist-based file type validation using magic byte checking, store uploaded files outside the web root or disable script execution in upload directories, and add proper authentication/authorization on file upload endpoints.
Fix this in Photokit
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49610 — 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-49610 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