CVE-2024-47946
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 · uneditedIf the attacker has access to a valid Poweruser session, remote code execution is possible because specially crafted valid PNG files with injected PHP content can be uploaded as desktop backgrounds or lock screens. After the upload, the PHP script is available in the web root. The PHP code executes once the uploaded file is accessed. This allows the execution of arbitrary PHP code and OS commands on the device as "www-data".
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 confidenceA file upload vulnerability in the desktop background/lock screen feature allows authenticated Powerusers to upload specially crafted PNG files containing injected PHP code. The application stores these files in the web root without proper validation, enabling the PHP code to execute when the file is accessed, resulting in arbitrary OS command execution as the www-data user.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 the application has a desktop background/lock screen upload featureReview the application documentation or navigate through the admin/user interface to locate any feature related to desktop backgrounds, lock screens, or wallpapers that accepts file uploadsAffected if The application includes a feature that allows uploading custom background images or lock screen content
-
Determine if Poweruser role has upload permissions for this featureCheck the application's role-based access control (RBAC) settings or user role documentation to see if users with Poweruser privileges can access the background/lock screen upload functionalityAffected if Poweruser accounts are permitted to upload files through this feature
-
Inspect where uploaded background images are storedLocate the upload directory for the background/lock screen feature by checking the application's configuration files, file system paths referenced in the code, or by uploading a test file and examining its storage locationAffected if Uploaded files are stored within the web root directory (public_html, www, htdocs, or similar)
-
Verify if PHP execution is disabled in the upload directoryCheck the web server configuration (Apache .htaccess, Nginx config, or equivalent) for the upload directory to see if PHP execution is explicitly disabled, or check if the application stores files with non-PHP extensionsAffected if PHP execution is allowed in the directory where uploaded background images are stored, or files are saved with executable extensions
-
Check the application's installed versionQuery the application's version number through its admin panel, CLI tool, or by inspecting version files in the installation directoryAffected if The installed version falls within any affected version range (compare against any official vulnerability advisories for this CVE)
Your environment is affected if the application has an active desktop background/lock screen upload feature accessible to Powerusers, and uploaded files are stored within the web root with PHP execution enabled in that directory.
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 file type validation using magic byte inspection, store uploads outside the web root, and disable PHP execution in upload directories.
- 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-47946 — 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-47946 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