CVE-2025-10229VulnerabilityPublished 10 Sep 2025Updated 15 Sep 2025

CVE-2025-10229: Freshwork · Open Redirect

Affects FreshworkSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 1.2.3 : update Freshwork when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.2.3

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Freshwork	Affected =1.2.0 =1.2.1 =1.2.2 =1.2.3	Fixed in–

AI-suggested

European organizations should immediately upgrade Freshwork to version 1.2.3 or later, where the vulnerability is fixed. Until the upgrade is applied, organizations should implement strict input validation and sanitization on the post_logout_redirect_uri parameter to ensure only trusted URLs are accepted. Employing a whitelist of allowed redirect domains can prevent arbitrary redirection. Additionally, security teams should monitor logs for suspicious logout redirect requests and educate users about the risks of clicking on unexpected links, especially those related to logout or session termination. Implementing web application firewalls (WAFs) with rules to detect and block open redirect attempts targeting this endpoint can provide an additional layer of defense. Finally, organizations should review their phishing detection and response capabilities to mitigate potential social engineering attacks leveraging this vulnerability.

Description

A vulnerability has been found in Freshwork up to 1.2.3. This impacts an unknown function of the file /api/v2/logout. Such manipulation of the argument post_logout_redirect_uri leads to open redirect. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.2.3 will fix this issue. You should upgrade the affected component. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using Freshwork, this vulnerability poses a moderate risk primarily in the form of social engineering and phishing attacks. Attackers could exploit the open redirect to craft URLs that appear legitimate but redirect users to malicious websites, potentially leading to credential theft or malware infection. This can undermine user trust in the affected service and may lead to reputational damage, especially for organizations handling sensitive customer data or regulated industries such as finance, healthcare, or government. While the vulnerability does not directly compromise system confidentiality or availability, the indirect consequences of successful phishing campaigns can be severe. Additionally, compliance with GDPR and other data protection regulations may be impacted if user data is compromised following exploitation.

Summary

CVE-2025-10229 is an open redirect vulnerability identified in Freshwork versions up to and including 1.2.3. The vulnerability resides in the /api/v2/logout endpoint, specifically in the handling of the post_logout_redirect_uri parameter. An attacker can manipulate this parameter to redirect users to arbitrary external URLs after logout, potentially leading to phishing attacks, session hijacking, or other social engineering exploits. The vulnerability is remotely exploitable without requiring authentication or privileges, and user interaction is necessary to trigger the redirect. The CVSS v4.0 base score is 5.3, indicating a medium severity level. The vendor has been notified but did not respond, and an upgrade to version 1.2.3 is advised to remediate the issue. No known exploits are currently reported in the wild. The vulnerability does not impact confidentiality or availability directly but can affect user trust and integrity of user sessions by facilitating redirection to malicious sites.

References

Community reviews

Loading reviews…