# CVE-2025-46612: File upload in n/a

> Remote attackers can execute arbitrary commands by uploading a JSP file via the Panel Designer dashboard after logging in with weak default credentials.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 10 Jun 2025
- **Also known as:** GHSA-v96f-2g2g-34fx

## What is CVE-2025-46612?

CVE-2025-46612 is a high-severity vulnerability in n/a, published on 10 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Panel Designer dashboard in Airleader Master and Easy before 6.36 allows remote attackers to execute arbitrary commands via a wizard/workspace.jsp unrestricted file upload. To exploit this, the attacker must login to the administrator console (default credentials are weak and easily guessable) and upload a JSP file via the Panel Designer dashboard.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 2 products.


Products: Airleader Easy Firmware, Airleader Master Ii\+ Firmware.

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

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

## Is CVE-2025-46612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46612 is a high-severity vulnerability in n/a, published on 10 Jun 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-46612 exists.

Affected product: n/a. 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-46612/ (Markdown: https://insights.sbomify.com/CVE-2025-46612/index.md)
```

## Sources

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

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