# CVE-2026-129262: File upload in Wubang Five-in-One Safety Production Management Information System

> Remote attackers can upload arbitrary files via the DiyFileUpload function of Wubang Five-in-One Safety Management Information System.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 14 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-pg2p-p23v-9vj6

## What is CVE-2026-129262?

CVE-2026-129262 is a medium-severity unrestricted file upload vulnerability in Wuxi Wubang Security Software Wubang Five-in-One Safety Production Management Information System, published on 14 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in Wuxi Wubang Security Software Wubang Five-in-One Safety Production Management Information System up to 3.5. Affected by this vulnerability is the function DiyFileUpload of the file /ws.asmx. This manipulation causes unrestricted upload. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-129262?

It affects 1 product.

An affected version is exposed as installed. No special setting or call is needed.


Products: Wuxi Wubang Security Software Wubang Five-in-One Safety Production Management Information System.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:wuxi_wubang_security_software:wubang_five-in-one_safety_production_management_information_system:*:*:*:*:*:*:*:*` from 3.0 up to 3.0
- `cpe:2.3:a:wuxi_wubang_security_software:wubang_five-in-one_safety_production_management_information_system:*:*:*:*:*:*:*:*` from 3.1 up to 3.1
- `cpe:2.3:a:wuxi_wubang_security_software:wubang_five-in-one_safety_production_management_information_system:*:*:*:*:*:*:*:*` from 3.2 up to 3.2
- `cpe:2.3:a:wuxi_wubang_security_software:wubang_five-in-one_safety_production_management_information_system:*:*:*:*:*:*:*:*` from 3.3 up to 3.3
- `cpe:2.3:a:wuxi_wubang_security_software:wubang_five-in-one_safety_production_management_information_system:*:*:*:*:*:*:*:*` from 3.4 up to 3.4
- `cpe:2.3:a:wuxi_wubang_security_software:wubang_five-in-one_safety_production_management_information_system:*:*:*:*:*:*:*:*` from 3.5 up to 3.5

## How do I fix CVE-2026-129262?

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

## Is CVE-2026-129262 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129262 and fix it if it is affected.

What it is: CVE-2026-129262 is a medium-severity unrestricted file upload vulnerability in Wuxi Wubang Security Software Wubang Five-in-One Safety Production Management Information System, published on 14 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129262 exists.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Wuxi Wubang Security Software Wubang Five-in-One Safety Production Management Information System. 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-129262/ (Markdown: https://insights.sbomify.com/CVE-2026-129262/index.md)
```

## Sources

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

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