CVE-2025-52204
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 · uneditedA Cross-Site Scripting (XSS) vulnerability exists in Znuny::ITSM 6.5.x in the customer.pl endpoint via the OTRSCustomerInterface parameter
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 confidenceCross-Site Scripting (XSS) vulnerability in Znuny::ITSM 6.5.x in the customer.pl endpoint via the OTRSCustomerInterface parameter. The vulnerability allows injection of malicious scripts through unsanitized user input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 Znuny::ITSM installation versionCheck the installed Znuny::ITSM version by inspecting the system package manager, application metadata, or the Znuny admin interface. Common commands include looking at the OTRS/znuny version file or checking the package version through the system package manager.Affected if The installed version falls within the 6.5.x branch (e.g., 6.5.0 through 6.5.x). Versions outside this branch are not affected by this specific CVE.
-
Confirm customer.pl endpoint is accessibleVerify that the customer.pl web interface is exposed and accessible in the deployment. This is typically found in the web root directory under /customer.pl or /otrs/customer.pl.Affected if The customer.pl endpoint is reachable via HTTP/HTTPS and accepts user requests.
-
Verify OTRSCustomerInterface parameter usageInspect web server logs or application configuration to determine if the OTRSCustomerInterface parameter is being used in customer.pl requests. This parameter controls the customer interface module selection.Affected if The OTRSCustomerInterface parameter is actively used in requests to customer.pl, either through URL parameters or form submissions.
-
Inspect input sanitization for OTRSCustomerInterfaceExamine the customer.pl source code or application logs to check whether the OTRSCustomerInterface parameter undergoes proper input validation and output encoding before being rendered. Look for sanitization functions or lack thereof in the code handling this parameter.Affected if The OTRSCustomerInterface parameter input is not sanitized or encoded before output, allowing unsanitized user input to be reflected in the page.
A user is affected if they run Znuny::ITSM version 6.5.x with the customer.pl endpoint accessible and the OTRSCustomerInterface parameter in use without proper input sanitization applied to that parameter.
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 dataImplement proper input validation and output encoding on the OTRSCustomerInterface parameter in customer.pl to prevent script injection.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52204 — 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-52204 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