Open redirect via unvalidated logout URL
Published Sep 10, 2025 · Updated Sep 10, 2025
Open redirect in Freshwork 1.2.3 and earlier allows remote attackers to redirect users via the post_logout_redirect_uri parameter. The /api/v2/logout endpoint uses the attacker-controlled parameter as a redirect destination without validating that it is trusted. No authentication is required, but a user must follow a crafted logout link; the bounded consequence is redirection to an untrusted site.
Summary
What happened
Open redirect in Freshwork 1.2.3 and earlier allows remote attackers to redirect users via the post_logout_redirect_uri parameter. The /api/v2/logout endpoint uses the attacker-controlled parameter as a redirect destination without validating that it is trusted. No authentication is required, but a user must follow a crafted logout link; the bounded consequence is redirection to an untrusted site.
The record
- CVE
- CVE-2025-10229
- Published
- Sep 10, 2025
- Updated
- Sep 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-601, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2025CVE publishedPublication date reported by the CVE source.
- Sep 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Public Freshwork logout redirect proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo