Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-4296 Overview
CVE-2025-4296 is an Open Redirect vulnerability [CWE-601] affecting HotelRunner B2B. The flaw allows attackers to craft URLs that redirect users from the legitimate HotelRunner B2B domain to attacker-controlled destinations. Exploitation requires user interaction, typically clicking a manipulated link. The vulnerability affects all HotelRunner B2B versions released before 04.06.2025. Attackers commonly abuse open redirects to support phishing campaigns, credential harvesting, and malware distribution by leveraging the trust users place in the originating domain.
Critical Impact
Attackers can abuse the trusted HotelRunner B2B domain to redirect authenticated or unauthenticated users to malicious sites, enabling phishing and forceful browsing attacks.
Affected Products
- HotelRunner B2B versions released before 04.06.2025
Discovery Timeline
- 2025-07-23 - CVE-2025-4296 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-4296
Vulnerability Analysis
The vulnerability resides in a URL redirection mechanism within the HotelRunner B2B application. The application accepts a user-controlled parameter that specifies a target URL and then issues an HTTP redirect to that destination without validating whether it points to an approved location. This class of flaw is tracked as [CWE-601] URL Redirection to Untrusted Site.
Because the redirect originates from the legitimate HotelRunner B2B domain, security controls that rely on domain reputation, including email gateways and web filters, may treat the initial link as trusted. Users who inspect the visible hostname before clicking are unlikely to detect the abuse.
The advisory also describes the impact as enabling Forceful Browsing. This indicates that redirect handling can be leveraged to reach application states or resources that would otherwise be protected by workflow controls.
Root Cause
The root cause is missing or insufficient validation of the redirect target. The application does not enforce an allowlist of permitted destinations and does not restrict redirects to relative paths on the same origin. Any host supplied through the vulnerable parameter is honored.
Attack Vector
An attacker crafts a URL that points to the HotelRunner B2B host and embeds an attacker-controlled destination in the vulnerable redirect parameter. The attacker distributes this URL through email, messaging platforms, or malicious advertising. When a victim clicks the link, the application redirects the browser to the attacker's site, which typically mimics a HotelRunner login page to harvest credentials or delivers malicious payloads.
Refer to the USOM Advisory TR-25-0169 and the Siber Güvenlik Notification for the authoritative technical description.
Detection Methods for CVE-2025-4296
Indicators of Compromise
- HTTP 30x responses from HotelRunner B2B endpoints containing Location headers pointing to external, non-HotelRunner domains.
- Inbound requests to HotelRunner B2B URLs containing suspicious query parameters carrying fully qualified external URLs or encoded variants.
- Referrer logs on external phishing infrastructure showing HotelRunner B2B as the previous hop.
Detection Strategies
- Inspect web server and reverse proxy logs for redirect parameters whose values decode to external hostnames.
- Correlate outbound user navigation with the preceding HotelRunner B2B response to identify redirect chains ending on untrusted domains.
- Add threat intelligence feeds covering phishing domains and match them against redirect destinations observed in traffic.
Monitoring Recommendations
- Enable full HTTP request and response logging on the HotelRunner B2B ingress, retaining URL parameters and Location headers.
- Alert on redirects whose target host does not match a maintained allowlist of HotelRunner domains.
- Monitor email gateway telemetry for messages containing HotelRunner B2B URLs with long or encoded query parameters.
How to Mitigate CVE-2025-4296
Immediate Actions Required
- Upgrade HotelRunner B2B to the version released on or after 04.06.2025, which contains the vendor fix.
- Audit outbound links and any integrations that generate HotelRunner B2B URLs to identify parameters that may be abused.
- Notify staff and partners of the risk and instruct them to verify the full URL, including query parameters, before clicking HotelRunner links received by email.
Patch Information
The vendor has resolved the issue in HotelRunner B2B releases dated 04.06.2025 and later. Coordination and publication were handled through Turkey's national CERT. Consult the USOM Advisory TR-25-0169 for vendor-provided remediation details.
Workarounds
- Deploy a web application firewall rule that inspects HotelRunner B2B redirect parameters and blocks values containing external hostnames or protocol schemes such as http:// and https:// outside the allowed domain set.
- Configure email security gateways to rewrite or sandbox HotelRunner B2B URLs so redirect targets are evaluated before user click-through.
- Educate users to hover over links and examine the complete URL, including any url=, next=, or redirect= parameters, before authenticating.
# Example NGINX rule to block external redirect targets in a HotelRunner-style parameter
# Adjust parameter name and allowed hosts to match production configuration
if ($arg_url ~* "^(https?:)?//(?!([a-z0-9-]+\.)*hotelrunner\.com)") {
return 400;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

