CVE-2026-71620 File upload in n/a
High 8.1
Published
Updated
Check this codebase for CVE-2026-71620 and fix it if it is affected.
What it is: CVE-2026-71620 is a high-severity vulnerability in n/a, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71620 in the wild and no public exploit code.
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-2026-71620/ (Markdown: https://insights.sbomify.com/CVE-2026-71620/index.md)
Remote attackers can execute arbitrary code by uploading a malicious PHP file to the ApiAdmin web application.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-71620?
CVE-2026-71620 is a high-severity vulnerability in n/a, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
File Upload vulnerability in Zhao-github ApiAdmin v.5.0.1 allows a remote attacker to execute arbitrary code via a crafted .php file
Weakness: CWE-434
Which versions are affected by CVE-2026-71620?
How do I fix CVE-2026-71620?
No fix has been published for CVE-2026-71620 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-71620 being exploited?
There is no known exploitation of CVE-2026-71620 in the wild and no public exploit code.
Sources
Also known as GHSA-g787-gm67-jg2v.