CVE-2026-6574
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 has been found in osuuu LightPicture up to 1.2.2. This issue affects some unknown processing of the file /public/install/lp.sql of the component API Upload Endpoint. Such manipulation of the argument key leads to hard-coded credentials. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA hardcoded credential vulnerability exists in the LightPicture image hosting application up to v1.2.2. The issue is in the API upload endpoint at /public/install/lp.sql, where the 'key' argument can be manipulated to authenticate using embedded credentials. This allows remote attackers to potentially upload files or gain unauthorized access to the system.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 installationIdentify if LightPicture image hosting application is running by checking for its web files, checking HTTP headers, or reviewing installed packages/software inventoriesAffected if LightPicture is installed and no version check has been performed
-
Check application versionLocate the version file or header within the LightPicture installation directory and compare the version number to v1.2.2Affected if The installed version is v1.2.2 or earlier (no patch applied)
-
Verify install directory existsCheck if the /public/install/ directory or lp.sql file is present on the web serverAffected if The /public/install/ directory and lp.sql file are still accessible on the server
-
Test API endpoint accessibilityAttempt a request to the /public/install/lp.sql endpoint or the API upload endpoint to see if it respondsAffected if The endpoint responds without requiring authentication or returns credential-related data
-
Inspect lp.sql for hardcoded credentialsIf lp.sql is accessible, open it and search for hardcoded API keys, passwords, or authentication tokens in the key argument or SQL dataAffected if Embedded credentials or manipulable key values are found in the lp.sql file
You are affected if LightPicture v1.2.2 or earlier is installed AND the /public/install/ directory with lp.sql is still present and accessible on the server.
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 dataRemove the /public/install/ directory from production deployments (installation files should not persist). Implement dynamic credential generation and proper authentication. If a patch becomes available, apply it immediately. Consider disabling the API upload endpoint until the vendor releases a fix.
- 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-2026-6574 — 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-2026-6574 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