CVE-2024-1921
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 · uneditedA vulnerability, which was classified as critical, was found in osuuu LightPicture up to 1.2.2. Affected is an unknown function of the file /app/controller/Setup.php. The manipulation leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-254856.
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 confidenceUnrestricted file upload vulnerability in LightPicture <=1.2.2 allows remote attackers to upload arbitrary files (likely including executable PHP code) via the Setup.php controller. The lack of proper file validation (type, extension, content) on uploaded files enables remote code execution when uploaded malicious files are accessed through the web server.
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>= 1.2.0, <= 1.2.2CVSS 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 LightPicture installationLocate the LightPicture application directory on your server. Look for the presence of typical LightPicture files such as index.php, Setup.php, or composer.json in your web server's document root.Affected if The LightPicture application directory is found on the server.
-
Identify installed versionCheck the version file or composer.json in the application root directory for a version declaration, or inspect any version information displayed in the application interface or setup page.Affected if The installed version is 1.2.0, 1.2.1, or 1.2.2.
-
Verify Setup.php existsCheck for the presence of Setup.php in the application root or controller directory. This is the vulnerable endpoint referenced in the CVE.Affected if The Setup.php file exists in the LightPicture installation.
-
Test upload functionality accessibilityAttempt to access the Setup.php endpoint via HTTP/HTTPS to confirm it is reachable. If authentication or setup completion is required, note whether the upload functionality can be triggered.Affected if The Setup.php endpoint is accessible without proper authentication or validation.
-
Check web server upload handlingReview the web server configuration and application settings to confirm file uploads are enabled. Inspect any upload-related configuration in the application.Affected if File uploads are enabled and the application accepts files through the vulnerable endpoint.
If LightPicture versions 1.2.0 through 1.2.2 are installed and the Setup.php upload endpoint is accessible, the environment is affected by this unrestricted file upload vulnerability.
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 if available, or implement strict server-side file validation (allowlist approved extensions, verify magic bytes/MIME type, rename files, store uploads outside webroot or with execution disabled).
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1921 — 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-1921 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