# CVE-2026-120224: Oray Pugongying X5 Pro API Authorization run_async_task improper authorization


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-6494-g389-mxj7

## What is CVE-2026-120224?

CVE-2026-120224 is a critical vulnerability in Oray Pugongying X5 Pro, published on 1 Nov 2026. 

### Official description

A security flaw has been discovered in Oray Pugongying X5 Pro up to 7.6.1. Affected is the function run_apis_by_json/run_async_task of the component API Authorization. The manipulation results in improper authorization. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-120224 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120224 is a critical vulnerability in Oray Pugongying X5 Pro, published on 1 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120224 exists.

Affected product: Oray Pugongying X5 Pro. 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-120224/ (Markdown: https://insights.sbomify.com/CVE-2026-120224/index.md)
```

## Sources

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

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