# Badaso CMS file upload vulnerability

Advisory record · `GHSA-gqp9-jh35-439m`

- **Identifiers:** `GHSA-gqp9-jh35-439m` · `CVE-2025-52353` · `PKSA-rkhj-gx6y-ns31`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-434](https://cwe.mitre.org/data/definitions/434.html)
- **Tags:** [Unrestricted file upload](https://agentprime.io/advisories/tag/file-upload.md)
- **Published:** 26 Aug 2025
- **Updated:** 26 Aug 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 Aug 2025, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `badaso/core` (Packagist): affected `<=2.9.11`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Badaso CMS badaso/core versions up to and including 2.9.11 are vulnerable to arbitrary code execution through the Media Manager file upload. An authenticated user can upload a file containing embedded PHP code that bypasses content-type checks, and the server executes it when the file is accessed by URL, which can lead to full compromise of the host. No fix is listed; the source gives few details on remediation.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0070, the 53rd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gqp9-jh35-439m)

## Sources

- [GitHub Advisory Database: GHSA-gqp9-jh35-439m](https://github.com/advisories/GHSA-gqp9-jh35-439m)
- [OSV: GHSA-gqp9-jh35-439m](https://osv.dev/vulnerability/GHSA-gqp9-jh35-439m)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-52353>
- <https://github.com/uasoft-indonesia/badaso>
- <https://medium.com/@pat.sanitjairak/remote-code-execution-in-a-plain-view-0f86f183543d>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gqp9-jh35-439m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gqp9-jh35-439m/>. Everything for agents: <https://agentprime.io/llms.txt>.
