CVE-2023-23074
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 · uneditedCross site scripting (XSS) vulnerability in Zoho ManageEngine ServiceDesk Plus 14 via embedding videos in the language component.
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 · moderate confidenceCross-site scripting (XSS) vulnerability in Zoho ManageEngine ServiceDesk Plus version 14 allows attackers to inject malicious scripts through the video embedding feature within the language component. The application fails to properly sanitize user-supplied video-related input (likely iframe, embed, or video tags), enabling stored or reflected XSS attacks when other users view the affected content.
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= 14.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.
-
Verify ServiceDesk Plus versionAccess the ServiceDesk Plus admin console or about page, typically found at /about.do or through the administrator settings panel. Alternatively, check the installation directory for version.txt or similar version manifest files.Affected if The installed version is exactly 14.0 (build 14000). Version 14.0 is the specific affected version.
-
Confirm video embedding feature existsNavigate to the language component settings within the admin console. Look for options related to video embedding, media insertion, or multimedia content in the language/localization settings area.Affected if The video embedding feature is present and accessible in the language component configuration.
-
Check for unsanitized video input handlingInspect the application's input handling for video-related fields (likely accepting iframe, embed, or video tags). Test submitting HTML tags like <script>, <iframe src=...>, <embed>, or <video> in the video embedding input fields within the language settings.Affected if The application accepts and stores HTML tags without sanitization or encoding in the video embedding inputs, allowing scripts to persist (stored XSS) or reflect back (reflected XSS).
A user is affected if they are running ServiceDesk Plus version 14.0 and have the video embedding feature enabled in the language component, with the application failing to sanitize video-related HTML input.
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 dataUpgrade to the latest patched version of ServiceDesk Plus. Alternatively, implement strict input validation and output encoding for the video embedding functionality in the language component, and deploy a Content Security Policy (CSP) to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23074 — 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-2023-23074 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