
Reflected XSS in Opixido OCMS admin/TUI/index.php (img parameter)
VulDB entry: https://vuldb.com/vuln/437282
CVE: CVE-2026-129254
CWE: CWE-79 — Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting")
Vendor / Product: Opixido OCMS
Repository: https://github.com/opixido/opixido-ocms
Affected component: admin/TUI/index.php
Vulnerable parameter: img
Affected revision: up to commit b7c15660aba83d96677c1a9abaa69c082a24f21c
Discovery date: 2026-10-19
Researcher: Usama Hanif (GitHub)
Disclosure status: Vendor contacted; no response. Reported to VulDB and accepted as VDB-437282 / CVE-2026-129254 on 2026-11-13.
A reflected cross-site scripting (XSS) vulnerability exists in the img parameter of the /admin/TUI/index.php endpoint in Opixido OCMS. Attacker-controlled input supplied through this parameter is reflected into the page without sufficient output encoding, allowing arbitrary JavaScript to execute in the application's origin.
Further testing showed that the injected JavaScript could access and exfiltrate JavaScript-readable authentication and session cookies to an attacker-controlled HTTP listener. The affected cookies were gs_admin (apparent CMS authentication cookie) and PHPSESSID (PHP session cookie). Cookie disclosure was confirmed; session impersonation using the disclosed values was not tested and is not claimed.
File: admin/TUI/index.php
Parameter: img
Attacker-controlled input reaches a JavaScript execution context without contextual encoding. By supplying a script-closing sequence followed by a new <script> element, an attacker can cause the browser to interpret injected content as executable JavaScript. This violates the trust boundary between untrusted HTTP request parameters and executable browser content.
(Add the exact file/line number here once confirmed against the upstream revision.)
http://127.0.0.1:8080</script><script>alert(document.domain)</script>
http://127.0.0.1:8080/admin/TUI/index.php?img=%3C%2Fscript%3E%3Cscript%3Ealert(document.domain)%3C%2Fscript%3E
See poc/payload.txt for the raw payload and request.
The browser executes the injected JavaScript and displays an alert() containing document.domain, confirming arbitrary JavaScript execution via the reflected img parameter.
See /poc-demo.mp4.
The application should treat the img parameter as untrusted data and encode it safely for the context in which it is rendered. The payload above should not execute.
Using an authenticated administrator session in an isolated local installation, a JavaScript callback executed through the vulnerable parameter sent an HTTP POST request to a local listener on 127.0.0.1:9001. The listener received values corresponding to the gs_admin and PHPSESSID cookies (redacted below).
[+] XSS callback received from 127.0.0.1
[+] Path: /
[+] Data: gs_admin=[REDACTED]; PHPSESSID=[REDACTED]
HTTP/1.1 204 No Content
No third-party cookies were collected and no session impersonation was attempted.
Depending on the victim's authentication state and the deployment's security controls, exploitation could allow:
<?php
$safeImage = json_encode(
$_GET['img'] ?? '',
JSON_HEX_TAG |
JSON_HEX_AMP |
JSON_HEX_APOS |
JSON_HEX_QUOT |
JSON_INVALID_UTF8_SUBSTITUTE
);
?>
<script>
const image = <?= $safeImage ?>;
</script>
This is a recommended encoding pattern, not a verified drop-in patch — apply the fix at the actual source-to-sink location in the upstream code.
Validate img against its intended purpose (e.g. an allow-list of known-good values) and reject unexpected input.
Where compatible with the application, set HttpOnly, Secure (over HTTPS), and an appropriate SameSite policy on authentication/session cookies. This is defense in depth and does not replace fixing the XSS.
Consider a restrictive CSP that limits script execution and avoids unsafe inline JavaScript.
Verify the PoC payload is treated as data (not executed) after remediation. Review related parameters (curName, curTable, curChamp) for similar unsafe output handling.
| Date | Event |
|---|---|
| 2026-10-19 | Vulnerability discovered |
| 2026-10-19 | Vendor notified |
| — | No vendor response received |
| 2026-11-13 | Accepted by VulDB as VDB-437282 / CVE-2026-129254 |
Discovered and reported by Usama Hanif (GitHub).