# CVE-2025-12630: Upload.am File Hosting VPN < 1.0.1 - Contributor+ Arbitrary Option Disclosure

> Contributors can view sensitive site options due to missing capability checks in the Upload.am WordPress plugin.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2025
- **Updated:** 2 Dec 2025
- **Also known as:** GHSA-9688-4r62-68pj

## What is CVE-2025-12630?

CVE-2025-12630 is a medium-severity missing authorization vulnerability in Unknown Upload.am, published on 2 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Upload.am  WordPress plugin before 1.0.1 is vulnerable to arbitrary option disclosure due to a missing capability check on its AJAX request handler, allowing users such as contributor to view site options.

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


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

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

## Is CVE-2025-12630 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12630 is a medium-severity missing authorization vulnerability in Unknown Upload.am, published on 2 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12630 exists.

Affected product: Unknown Upload.am. 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-12630/ (Markdown: https://insights.sbomify.com/CVE-2025-12630/index.md)
```

## Sources

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

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