Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-129254 — Reflected XSS in Opixido OCMS admin/TUI/index.php (img parameter) | Kitploit
Tools/GitHubGitHub/usama-hanif131/cve-2026-129254
Vulnerability AnalysisExploitationWeb Application ExploitationWeb Security
GitHubusama-hanif131/cve-2026-129254

CVE-2026-129254

Reflected XSS in Opixido OCMS admin/TUI/index.php (img parameter)

View Repository
6 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    962
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    558
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    348
  • 4

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    344
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    324
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    297

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-129254 — Reflected XSS in Opixido OCMS (Admin TUI)

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.


1. Summary

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.

2. Affected Component and Root Cause

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.)

3. Proof of Concept

Test environment

  • OS: Kali Linux
  • Application: Opixido OCMS
  • Web server: PHP built-in development server
  • PHP version: 8.4.24
  • Database: MariaDB
  • Browser: Chromium-based
  • Tooling: Burp Suite Professional
  • Local URL: http://127.0.0.1:8080

Payload

</script><script>alert(document.domain)</script>

Request

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.

Observed behavior

The browser executes the injected JavaScript and displays an alert() containing document.domain, confirming arbitrary JavaScript execution via the reflected img parameter.

Video demonstration

See /poc-demo.mp4.

Expected behavior

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.

4. Additional Impact — Session Cookie Disclosure

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.

5. Security Impact

Depending on the victim's authentication state and the deployment's security controls, exploitation could allow:

  • Disclosure of JavaScript-accessible authentication and session cookies.
  • Access to same-origin application content available to the victim.
  • Unauthorized interaction with authenticated application functionality.
  • Exposure of sensitive application information accessible through the victim's browser.
  • Potential session impersonation if disclosed credentials are reusable.

6. Recommended Remediation

6.1 Use safe JavaScript serialization

<?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.

6.2 Validate the parameter

Validate img against its intended purpose (e.g. an allow-list of known-good values) and reject unexpected input.

6.3 Harden session cookies

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.

6.4 Add a Content Security Policy

Consider a restrictive CSP that limits script execution and avoids unsafe inline JavaScript.

6.5 Add regression tests

Verify the PoC payload is treated as data (not executed) after remediation. Review related parameters (curName, curTable, curChamp) for similar unsafe output handling.

7. Disclosure Timeline

DateEvent
2026-10-19Vulnerability discovered
2026-10-19Vendor notified
—No vendor response received
2026-11-13Accepted by VulDB as VDB-437282 / CVE-2026-129254

8. Credits

Discovered and reported by Usama Hanif (GitHub).

Download Tool