CVE-2026-6574: Hard-coded Credentials in osuuu LightPicture
A 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.
AI Analysis
Technical Summary
This vulnerability in osuuu LightPicture (up to version 1.2.2) arises from hard-coded credentials linked to the handling of the /public/install/lp.sql file within the API Upload Endpoint. The issue allows remote attackers to potentially leverage these credentials due to improper processing of an argument key. The CVSS 4.0 base score is 6.9, indicating a medium severity with network attack vector, no privileges or user interaction required, and low to limited impact on confidentiality, integrity, and availability. The vendor has not issued any patch or official remediation, and the vulnerability remains unmitigated as of the publication date.
Potential Impact
The presence of hard-coded credentials can allow remote attackers to gain unauthorized access or perform actions with elevated privileges on affected versions of osuuu LightPicture. This can compromise the confidentiality, integrity, and availability of the system to a limited extent. Since the vulnerability requires no privileges or user interaction and can be exploited remotely, it poses a tangible risk. However, the impact is rated medium due to the limited scope of the credential exposure and the lack of confirmed active exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vendor has not responded and no official fix is available, users should consider mitigating exposure by restricting access to the vulnerable API Upload Endpoint, removing or securing the /public/install/lp.sql file if possible, and monitoring for unusual activity related to this component. Applying compensating controls such as network-level restrictions or application-layer protections may reduce risk until an official patch is released.
CVE-2026-6574: Hard-coded Credentials in osuuu LightPicture
Description
A 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.
CVSS v4.0
Score 6.9medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in osuuu LightPicture (up to version 1.2.2) arises from hard-coded credentials linked to the handling of the /public/install/lp.sql file within the API Upload Endpoint. The issue allows remote attackers to potentially leverage these credentials due to improper processing of an argument key. The CVSS 4.0 base score is 6.9, indicating a medium severity with network attack vector, no privileges or user interaction required, and low to limited impact on confidentiality, integrity, and availability. The vendor has not issued any patch or official remediation, and the vulnerability remains unmitigated as of the publication date.
Potential Impact
The presence of hard-coded credentials can allow remote attackers to gain unauthorized access or perform actions with elevated privileges on affected versions of osuuu LightPicture. This can compromise the confidentiality, integrity, and availability of the system to a limited extent. Since the vulnerability requires no privileges or user interaction and can be exploited remotely, it poses a tangible risk. However, the impact is rated medium due to the limited scope of the credential exposure and the lack of confirmed active exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vendor has not responded and no official fix is available, users should consider mitigating exposure by restricting access to the vulnerable API Upload Endpoint, removing or securing the /public/install/lp.sql file if possible, and monitoring for unusual activity related to this component. Applying compensating controls such as network-level restrictions or application-layer protections may reduce risk until an official patch is released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-04-18T20:01:42.583Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e4dc9d19fe3cd2cd590f0e
Added to database: 4/19/2026, 1:46:05 PM
Last enriched: 4/27/2026, 12:24:18 AM
Last updated: 6/3/2026, 2:12:25 AM
Views: 101
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.