dbcve.org
MovideskApplication · Zenvia

CVE-2025-0970

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

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 declared as problematic. Affected by this vulnerability is an unknown functionality of the file /Account/Login. The manipulation of the argument ReturnUrl leads to open redirect. The attack can 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

An open redirect vulnerability exists in the Zenvia Movidesk login page (/Account/Login). The ReturnUrl parameter is not properly validated, allowing attackers to craft malicious URLs that redirect users to arbitrary external sites after authentication. This can be leveraged in phishing attacks to steal credentials or deliver malicious content.

MitigationUpgrade Movidesk to version 25.01.22.245a473c54 or later. Until the upgrade is applied, implement WAF rules to validate and sanitize the ReturnUrl parameter, restricting it to trusted domains only.

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

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

  1. Identify the Movidesk version
    Access the Movidesk admin panel or check the application footer/dashboard for the version number displayed (typically shown as something like 25.01.XX)
    Affected if The version displayed is 25.01.22 or lower (any version up to and including 25.01.22)
  2. Verify the login endpoint is exposed
    Confirm that the /Account/Login path is accessible in your Movidesk instance (navigate to your Movidesk URL followed by /Account/Login)
    Affected if The login page loads successfully at this path, meaning the vulnerable endpoint is exposed
  3. Test the ReturnUrl parameter for open redirect
    Use a browser or curl to request the login page with a ReturnUrl parameter pointing to an external domain, for example: https://your-movidesk-url/Account/Login?ReturnUrl=http://evil.com. Observe whether the application redirects to the external domain after login or displays the malicious URL in the response.
    Affected if After authentication, the user is redirected to the URL specified in ReturnUrl, especially if it points to an external/untrusted domain
  4. Check for WAF or proxy logging of suspicious ReturnUrl values
    Review WAF logs, application logs, or reverse proxy logs for requests to /Account/Login containing ReturnUrl parameters with external domains (http:// or https:// domains different from your own Movidesk domain)
    Affected if Logs show requests with external ReturnUrl values, indicating active probing or attempted exploitation

You are affected if your Movidesk version is 25.01.22 or lower AND the /Account/Login endpoint accepts external URLs in the ReturnUrl parameter, allowing unvalidated redirects to arbitrary domains.

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. Until the upgrade is applied, implement WAF rules to validate and sanitize the ReturnUrl parameter, restricting it to trusted domains only.

Recommended fix High confidence

25.01.22.245a473c54

  1. Create a backup of the current Movidesk database and application files before proceeding with the upgrade
  2. Download Movidesk version 25.01.22.245a473c54 from the official Zenvia vendor source
  3. Stop the Movidesk application services
  4. Deploy the upgraded version 25.01.22.245a473c54 to the production environment
  5. Restart the Movidesk application services
  6. Verify the application is functioning correctly and the ReturnUrl parameter on /Account/Login is now properly validated

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

Fix this in Movidesk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0970 — 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-0970 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