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-2026-55840 Overview
CVE-2026-55840 is an open redirect vulnerability [CWE-601] in Scoold, a Q&A and knowledge sharing platform for teams. The flaw affects the getBackToUrl() method in src/main/java/com/erudika/scoold/utils/HttpUtils.java in versions prior to 1.69.1. The method validates the backto and returnto parameters using Strings.CI.startsWith against the configured server URL. An attacker can supply an absolute URL whose hostname begins with the legitimate hostname, bypassing the prefix check. A victim who follows a crafted sign-in link can be redirected to an attacker-controlled domain after authentication. The issue is resolved in version 1.69.1.
Critical Impact
Successful exploitation enables phishing attacks and potential theft of credentials or authentication tokens through post-authentication redirects to attacker-controlled domains.
Affected Products
- Scoold versions prior to 1.69.1
- Erudika Scoold Q&A platform deployments
- Self-hosted Scoold instances using default URL validation
Discovery Timeline
- 2026-10-15 - CVE-2026-55840 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-55840
Vulnerability Analysis
The vulnerability resides in the getBackToUrl() method of the HttpUtils class. The method constructs a resolved URL by calling URI.create(serverUrl).resolve(backto) and then verifies the result starts with the configured server URL using case-insensitive string matching. This approach is unsafe because URI.resolve() returns the input URI unchanged when the input is an absolute URI with a different authority. If the attacker-supplied hostname begins with the legitimate server hostname as a prefix, the subsequent Strings.CI.startsWith check passes.
For example, if the server URL is https://scoold.example.com, an attacker can supply https://scoold.example.com.attacker.tld/path. The prefix check succeeds, and the user is redirected to the attacker domain after sign-in. The attacker-controlled page can then impersonate the legitimate application to harvest credentials or session tokens.
Root Cause
The root cause is improper URL validation [CWE-601]. The code relies on substring prefix matching rather than parsing the URL and comparing origin components (scheme, host, port). Prefix checks on serialized URLs do not enforce origin boundaries.
Attack Vector
Exploitation requires user interaction. An attacker crafts a sign-in link containing a malicious returnto or backto parameter and delivers it through phishing, chat, or social engineering. After the victim authenticates, Scoold redirects the browser to the attacker's domain.
// Patch from Scoold commit 9d61f6f - HttpUtils.java
String backto = Optional.ofNullable(StringUtils.stripToNull(req.getParameter("returnto"))).
orElse(Utils.urlDecode(HttpUtils.getStateParam("returnto", req)));
String serverUrl = CONF.serverUrl() + CONF.serverContextPath();
-String resolved = "";
+URI backtoURI = URI.create("");
try {
- resolved = URI.create(serverUrl).resolve(Optional.ofNullable(backto).orElse("")).toString();
+ backtoURI = URI.create(serverUrl).resolve(Optional.ofNullable(backto).orElse(""));
} catch (Exception e) {
logger.warn("Invalid return-to URI: {}", e.getMessage());
}
-if (!Strings.CI.startsWith(resolved, serverUrl)) {
+if (!isSameOrigin(backtoURI, URI.create(CONF.serverUrl()))) {
backto = "";
} else {
- backto = resolved;
+ backto = backtoURI.toString();
}
static boolean isSameOrigin(URI backtoURI, URI origin) {
try {
if (backtoURI.getHost() == null || origin.getHost() == null) {
return false;
}
// ... origin comparison continues
Source: GitHub Commit 9d61f6f
Detection Methods for CVE-2026-55840
Indicators of Compromise
- Authentication-related requests containing returnto or backto parameters pointing to external hostnames
- Query parameters where the hostname matches the legitimate server hostname as a prefix followed by additional characters (for example, scoold.example.com.attacker.tld)
- Spike in outbound redirects from the sign-in flow to domains not on the organization's allow list
Detection Strategies
- Inspect web server access logs for requests to /signin and related endpoints containing returnto or backto parameters with absolute URLs
- Deploy web application firewall rules that reject returnto/backto values whose host does not exactly match the configured Scoold origin
- Correlate referrer and redirect headers to identify post-authentication redirects leaving the trusted origin
Monitoring Recommendations
- Enable centralized logging of HTTP 3xx responses from Scoold with the resolved Location header value
- Alert on sign-in sessions followed immediately by outbound redirects to newly observed external domains
- Review phishing report queues for messages containing crafted Scoold sign-in URLs
How to Mitigate CVE-2026-55840
Immediate Actions Required
- Upgrade Scoold to version 1.69.1 or later as the primary remediation
- Audit historical access logs for suspicious returnto and backto parameters predating the upgrade
- Rotate any session tokens or credentials that may have been exposed through phishing campaigns leveraging this flaw
Patch Information
The fix is included in Scoold 1.69.1. The patch replaces the prefix string comparison with an isSameOrigin() check that compares host, scheme, and port of the resolved URI against the configured server origin. See the Scoold 1.69.1 release and the GitHub Security Advisory GHSA-85fm-6f2v-74pq for full details.
Workarounds
- Place Scoold behind a reverse proxy that strips or validates returnto and backto parameters before they reach the application
- Configure web application firewall rules to allow only relative paths in redirect parameters
- Train users to inspect post-authentication redirect destinations and report unexpected domains
# Example nginx rule to block absolute URLs in returnto/backto parameters
if ($arg_returnto ~* "^https?://") {
return 400;
}
if ($arg_backto ~* "^https?://") {
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

