dbcve.org
MovideskApplication · Zenvia

CVE-2025-0971

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-03
Fix available
A fix is available. Upgrade to after 25.01.22 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A vulnerability was found in Zenvia Movidesk up to 25.01.22. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /Account/EditProfile of the component Profile Editing. The manipulation of the argument username leads to cross site scripting. The attack may be launched 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 confidence

Zenvia Movidesk versions up to 25.01.22 contain a cross-site scripting (XSS) vulnerability in the /Account/EditProfile profile editing functionality. The 'username' parameter is not properly sanitized, allowing an authenticated attacker to inject malicious JavaScript that executes in other users' browsers when they view the affected profile.

MitigationUpgrade Movidesk to version 25.01.22.245a473c54 or later. As a defense-in-depth measure, implement input validation and output encoding on all user-supplied profile fields.

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
MovideskApplication
Affected:<= 25.01.22

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Zenvia Movidesk installation
    Locate the Movidesk application in your environment and identify the exact version number. This is typically found in the application about page, admin panel, or in the application binaries/config files.
    Affected if The product is Zenvia Movidesk with version 25.01.22 or earlier.
  2. Check version against affected range
    Compare your installed Movidesk version to the affected range of <= 25.01.22. If you cannot determine the exact version, check for any available version identifier in the application metadata or deployment artifacts.
    Affected if Your installed version is 25.01.22 or any version number lower than 25.01.22.
  3. Verify /Account/EditProfile endpoint exists
    Check if the /Account/EditProfile route is accessible in your Movidesk instance. This is typically found in the web application's routing configuration or by attempting to access the URL directly if you have application access.
    Affected if The /Account/EditProfile functionality exists and is accessible in your deployment.
  4. Confirm authenticated user access to profile editing
    Determine whether user authentication is enabled and whether standard users have access to the profile editing functionality. Review your authentication settings and user role permissions related to profile management.
    Affected if Authenticated users can access and modify their profiles through the EditProfile feature.
  5. Inspect username parameter handling
    If you have access to the application, review how the username field is processed in the profile editing code or intercept a profile save request to observe how the username parameter is handled. Look for evidence of input sanitization or lack thereof.
    Affected if The username parameter in /Account/EditProfile is not properly sanitized before being stored or displayed.

You are affected if you are running Zenvia Movidesk version 25.01.22 or earlier and the profile editing functionality is accessible to authenticated users in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 25.01.22
Interim mitigation

Upgrade Movidesk to version 25.01.22.245a473c54 or later. As a defense-in-depth measure, implement input validation and output encoding on all user-supplied profile fields.

Recommended fix High confidence

25.01.22.245a473c54

  1. 1. Ensure you have a complete backup of your Movidesk database and configuration before upgrading.
  2. 2. Download the fixed version 25.01.22.245a473c54 from the official Zenvia Movidesk distribution channel.
  3. 3. Apply the upgrade following the standard Movidesk upgrade documentation.
  4. 4. After upgrade, verify the /Account/EditProfile page works correctly.
  5. 5. Test that the username field properly sanitizes input and no XSS payload executes.
Caveat Standard upgrade risks apply - review release notes for any configuration or behavioral changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Movidesk Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0971 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0971 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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