# CVE-2025-1835: osuuu LightPicture Api.php upload unrestricted upload

> Remote attackers can upload malicious files via the Api.php upload function in LightPicture, potentially leading to code execution.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2025
- **Updated:** 3 Mar 2025
- **Also known as:** GHSA-cqg6-gpxx-hq82

## What is CVE-2025-1835?

CVE-2025-1835 is a medium-severity vulnerability in osuuu LightPicture, published on 2 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in osuuu LightPicture 1.2.2 and classified as critical. This vulnerability affects the function upload of the file /app/controller/Api.php. The manipulation of the argument file leads to unrestricted upload. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-1835?


## How do I fix CVE-2025-1835?

No fix has been published for CVE-2025-1835 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-1835 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1835 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1835 and fix it if it is affected.

What it is: CVE-2025-1835 is a medium-severity vulnerability in osuuu LightPicture, published on 2 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1835 exists.

Affected product: osuuu LightPicture. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1835/ (Markdown: https://insights.sbomify.com/CVE-2025-1835/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1835
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1835
- OSV: https://osv.dev/vulnerability/CVE-2025-1835

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1835/
Summaries are generated and may contain mistakes; the official description above is the record.