CVE-2025-0972
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 vulnerability classified as problematic has been found in Zenvia Movidesk up to 25.01.22. This affects an unknown part of the component New Ticket Handler. The manipulation of the argument subject leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 25.01.22.245a473c54 is able to address this issue. It is recommended to upgrade the affected 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 · high confidenceA stored cross-site scripting (XSS) vulnerability exists in Zenvia Movidesk's New Ticket Handler component. The subject argument is not properly sanitized, allowing attackers to inject malicious scripts that execute when other users view the ticket.
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<= 25.01.22CVSS 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.
-
Identify Zenvia Movidesk installationLocate the Movidesk application files or check system inventory/software list for Zenvia MovideskAffected if Zenvia Movidesk is installed in the environment
-
Check installed Movidesk versionAccess the Movidesk admin panel or check the application version information (typically found in About or System Info sections), or query the application's version endpoint if availableAffected if The installed version is 25.01.22 or lower (any version up to and including 25.01.22)
-
Verify New Ticket Handler is activeCheck if the New Ticket Handler feature is enabled in Movidesk configuration or settings (look for ticket creation/handler module settings)Affected if The New Ticket Handler component is enabled and accessible to users
-
Inspect existing tickets for suspicious subject contentQuery the ticket database or use Movidesk search to review ticket subjects for unusual characters such as <script>, javascript:, onload, onerror, or HTML tags that were not intentionally createdAffected if Any tickets exist with unsanitized script tags or event handlers in the subject field
A user is affected if Zenvia Movidesk version 25.01.22 or lower is installed AND the New Ticket Handler component is enabled, particularly if tickets with potentially malicious subject content exist in the system.
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.
dbcve · scopedUpgrade Zenvia Movidesk to version 25.01.22.245a473c54 or later to resolve the XSS vulnerability in the New Ticket Handler.
25.01.22.245a473c54
- Identify all Movidesk instances currently running version 25.01.22 or earlier
- Backup the current Movidesk installation and database before upgrading
- Download Movidesk version 25.01.22.245a473c54 from the official Zenvia vendor
- Follow the vendor's official upgrade procedure to install the new version
- After upgrade, verify the New Ticket Handler component is functioning correctly
- Test that the subject field in New Ticket Handler now properly sanitizes input to prevent XSS
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0972 — 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-0972 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