CVE-2025-70037
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 · uneditedAn issue pertaining to CWE-601: URL Redirection to Untrusted Site was discovered in linagora Twake v2023.Q1.1223. This allows attackers to obtain sensitive information and execute arbitrary code.
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 confidenceOpen redirect vulnerability (CWE-601) in linagora Twake v2023.Q1.1223 allows attackers to craft malicious URLs that redirect users to untrusted external sites. Attackers can leverage this for phishing attacks to obtain sensitive information or execute arbitrary code via malicious payloads delivered through the redirect.
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= 2023.q1.1223CVSS 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 installed Twake versionAccess the Twake administration panel or check the package.json/version file in the Twake installation directory. If using Docker, check the image tag or inspect the container metadata.Affected if The installed version is exactly 2023.q1.1223 (note: the version range shows an exact match with '=')
-
Verify web interface is accessibleConfirm that the Twake web interface is running and accessible to users or attackers. This is typically on ports 80/443 or configured custom ports.Affected if The web application is exposed and reachable over HTTP/HTTPS
-
Locate redirect functionalityInspect web application logs or network traffic for URL parameters that may control redirects (such as 'redirect', 'url', 'next', 'dest', or similar parameters). Check authentication-related endpoints that handle post-login navigation.Affected if The application processes user-controlled parameters in redirect URLs without strict allowlist validation
-
Test for untrusted redirect vectorsSubmit a crafted request with an external domain as a redirect target (e.g., ?redirect=https://attacker.com) to any authentication or navigation endpoint and observe if the response includes a Location header pointing to the untrusted domain.Affected if The application allows arbitrary external URLs in redirect parameters without sanitization
A user is affected if they are running exactly version 2023.q1.1223 of Linagora Twake and the web interface is accessible with unvalidated redirect parameters present.
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 strict URL validation using allowlists for permitted redirect destinations, sanitize all redirect input parameters, and avoid using untrusted user input directly in redirect URLs.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70037 — 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-70037 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