CVE-2025-33118
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM QRadar SIEM 7.5 through 7.5.0 Update Pack 12 is vulnerable to stored cross-site scripting. This vulnerability allows authenticated users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM QRadar SIEM versions 7.5 through 7.5.0 Update Pack 12 contain a stored cross-site scripting vulnerability in the Web UI. Authenticated users can inject malicious JavaScript code that persists in the application and executes in the browsers of other users viewing the affected content, potentially enabling session hijacking and credential theft within trusted sessions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm QRadar SIEM installationCheck for QRadar SIEM processes or services running on the system. On the QRadar console, run: ps -ef | grep -i qradarAffected if QRadar SIEM processes are not found, meaning the product is not installed.
-
Identify QRadar versionRun the command: /opt/qradar/bin/qradar_version or check the UI: Administration > System Settings > System Information to view the exact version and Update Pack number.Affected if The installed version is 7.5.0 through 7.5.0 Update Pack 12 (or any 7.5.x version within this range).
-
Verify Web UI is accessibleConfirm the QRadar Web UI is accessible by attempting to reach the console login page via browser or checking that the Apache/HTTP service is running: systemctl status httpd or ps -ef | grep httpdAffected if Web UI is not accessible or the HTTP service is not running (the vulnerability requires the Web UI to be exposed).
-
Confirm authentication is enabledVerify that user authentication to the Web UI is functioning. Check that local users or external authentication (LDAP/AD) is configured in Administration > Authentication > Authentication Methods.Affected if Authentication is disabled or no users exist (the XSS requires an authenticated user to inject the payload).
The environment is affected if QRadar SIEM version 7.5.0 through 7.5.0 Update Pack 12 is installed with the Web UI accessible and user authentication enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply available vendor patches or updates to QRadar SIEM. Implement output encoding and input validation for all user-supplied data in the Web UI, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-33118 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data