# CVE-2025-13932: Missing authorization in Monitoring Platform (Cloud API & Device Control API)

> Authenticated users can access detailed data of any plant by modifying the plant_id parameter in API requests.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-rj4p-qc9g-j2p3

## What is CVE-2025-13932?

CVE-2025-13932 is a high-severity missing authorization vulnerability in SolisCloud Monitoring Platform (Cloud API & Device Control API), published on 4 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SolisCloud API suffers from a Broken Access Control vulnerability, specifically an Insecure Direct Object Reference (IDOR), where any authenticated user can access detailed data of any plant by altering the plant_id in the request.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-13932 being exploited?

There is no known exploitation of CVE-2025-13932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13932 is a high-severity missing authorization vulnerability in SolisCloud Monitoring Platform (Cloud API & Device Control API), published on 4 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13932 in the wild and no public exploit code.

Affected product: SolisCloud Monitoring Platform (Cloud API & Device Control API). 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-13932/ (Markdown: https://insights.sbomify.com/CVE-2025-13932/index.md)
```

## Sources

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

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