CVE-2025-52650
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 · uneditedInline script execution allowed in CSP vulnerability has been identified in HCL AION v2.0
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 confidenceA Content Security Policy (CSP) vulnerability has been identified in HCL AION v2.0 that allows inline script execution. This defeats the purpose of CSP as a defense-in-depth mechanism against XSS attacks, potentially enabling attackers to inject and execute malicious scripts.
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= 2.0.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify HCL AION installation versionLocate the installed HCL AION version using product-specific commands or configuration files (e.g., check installation metadata, version file, or product dashboard)Affected if installed version is 2.0.0 (exact match)
-
Locate CSP configurationFind the CSP header configuration in HCL AION v2.0 - typically in web server configuration, reverse proxy settings, or application-level security headers configurationAffected if CSP is configured and actively applied to the application
-
Inspect CSP script-src directiveExamine the Content-Security-Policy header or configuration for the 'script-src' directive. Use browser DevTools (Network tab, Headers), curl -I against the application, or inspect the web server config filesAffected if script-src contains 'unsafe-inline' or lacks explicit restrictions on inline scripts
-
Verify inline script execution is possibleAttempt to access the application and check if inline JavaScript (e.g., <script>alert(1)</script>) executes or is blocked. Review browser console for CSP violations when testing inline scriptsAffected if inline scripts execute without triggering CSP violations
A user is affected if running HCL AION v2.0 with CSP headers that permit inline script execution via 'unsafe-inline' in the script-src directive.
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 dataConfigure CSP headers in HCL AION v2.0 to explicitly disallow inline script execution ('script-src 'self' 'unsafe-inline'') and use non-inline alternatives or nonce-based policies instead.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52650 — 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-52650 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