Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft sign-in URL with prefix-matching evil host
-
DeliveryDeliver phishing link to victim
-
ExploitPrefix check accepts attacker URL
-
ExecutionVictim authenticates and is redirected
-
ImpactHarvest credentials or session token
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Redirect URL validation
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to craft a sign-in URL whose backto or returnto parameter is an absolute URL whose hostname begins with the configured server hostname (e.g. example.com.evil.com), defeating the pre-1.69.1 Strings.CI.startsWith check in HttpUtils.getBackToUrl(). The critical LIMITING factor is user interaction: a victim must actively follow the crafted authentication link and complete sign-in for the redirect to fire (UI:R). No attacker authentication is needed (PR:N), and default configurations are affected, but impact is confined to post-authentication redirection to an attacker domain, so success also depends on the victim then disclosing credentials/tokens at the malicious site. Affected: all Scoold versions prior to 1.69.1. |
| Impact | This is a genuine but moderate-severity open redirect (CWE-601), not a top-tier priority. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N, score 5.4) is internally consistent with the description: network-reachable, low complexity, no authentication, but critically requiring user interaction (UI:R) because a victim must click the crafted sign-in link. Confidentiality and integrity impacts are LOW (C:L/I:L) - limited to credential/token exposure via post-authentication redirect - with no availability impact. No EPSS score was provided, so exploitation probability cannot be quantified. The CVE is NOT in CISA KEV and no public POC is referenced, meaning no public exploit identified at time of analysis. The real limiting factor is the mandatory phishing-style social-engineering step plus the fact that Scoold has a small deployment footprint, so mass exploitation is unlikely. The flaw and fix are strongly corroborated by the vendor commit diff, which replaces the weak Strings.CI.startsWith prefix check with a strict same-origin comparison (host, scheme, and port, plus userinfo rejection). No conflicting signals are present; the main gap is absent EPSS/exploitation-probability data. |
| Exploit ScenarioDerived | An attacker crafts a Scoold sign-in link whose backto/returnto parameter points to an absolute URL like https://example.com.evil.com/steal, where the hostname begins with the legitimate server hostname so the flawed startsWith prefix check passes. The attacker sends this link to a victim via phishing; after the victim authenticates, Scoold redirects them to the attacker-controlled domain, where credentials or OAuth/session tokens can be harvested. No public exploit code is identified, though the mechanism is simple and the fixing commit documents the exact bypass. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Open redirect in Scoold, Erudika's Java-based Q&A and knowledge-sharing platform, affects every release prior to 1.69.1, where the backto and returnto parameters handled by HttpUtils.getBackToUrl() are validated with a case-insensitive prefix match against the configured server URL. An unauthenticated attacker can craft a sign-in link whose backto value is an absolute URL on a look-alike host such as example.com.evil.com; URI.resolve() retains the attacker URL, the prefix check passes, and the victim is redirected to the attacker's domain after completing authentication. The result is phishing and possible credential or token theft on the malicious site, but exploitation hinges on the victim following the crafted link and signing in (UI:R); no public exploit code and no confirmed active exploitation have been identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade to Scoold 1.69.1, which replaces the vulnerable Strings.CI.startsWith prefix check in HttpUtils.getBackToUrl() with a strict isSameOrigin() comparison of scheme, host and effective port while rejecting userinfo and null-host URIs; the release is published at https://github.com/Erudika/scoold/releases/tag/1.69.1 and the source change is in commit 9d61f6fe15d4f9f6262812ba7fea43be8d5bb745, with advisory details at https://github.com/Erudika/scoold/security/advisories/GHSA-85fm-6f2v-74pq. If upgrading cannot be scheduled immediately, the only meaningful compensating control is an edge rule (reverse proxy, WAF or servlet filter) on the authentication endpoints that rejects any request whose backto or returnto parameter contains an absolute URL (scheme or double-slash authority) or embedded userinfo ('@'), allowing only relative, single-slash paths; the trade-off is that this blocks any legitimate deployment that has come to rely on absolute-URL return targets, and it must be maintained against the same look-alike-hostname edge cases (trailing-dot hosts, case variants, non-default ports) that the upstream fix handles, so it is a stopgap rather than an equivalent fix. Because the attack requires the victim to complete authentication and then voluntarily enter credentials on the attacker-controlled page, pairing either measure with user-facing guidance - and with monitoring for authentication redirects leaving the configured origin - reduces residual risk, but neither substitutes for the 1.69.1 upgrade.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a classic open redirect (CWE-601: URL Redirection to Untrusted Site) rooted in Java URI resolution semantics. HttpUtils.getBackToUrl() resolved the user-supplied backto/returnto value against the configured server URL with URI.create(serverUrl).resolve(backto), then validated the result with a case-insensitive Strings.CI.startsWith(resolved, serverUrl) prefix test. Because only a string prefix was compared, an absolute URL whose hostname merely begins with the legitimate hostname (for example https://example.com.evil.com/steal when the server URL is https://example.com) both survives URI.resolve() and satisfies the prefix check. The fix in commit 9d61f6fe15d4f9f6262812ba7fea43be8d5bb745 replaces the string comparison with an isSameOrigin() helper that parses both URIs and requires an exact, case-insensitive match of scheme and host plus equal effective ports (with 80/443 defaults inferred for http/https), and explicitly rejects URIs carrying userinfo (the https://evil.com@example.com construction) or a null host; exceptions return false. A new HttpUtilsTest suite covers the look-alike subdomain, scheme mismatch, port mismatch, userinfo, null-host and invalid-URI cases. The CPE cpe:2.3:a:erudika:scoold:*:*:*:*:*:*:*:* is version-wildcarded, so the vendor advisory is the authoritative source narrowing affected releases to those before 1.69.1. The assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N (5.4) reflects a network-reachable, unauthenticated attack that nonetheless requires victim interaction and yields only limited confidentiality and integrity impact on the redirected user.
Know when Scoold gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Remote unauthenticated attacker crafts a URL (AV:N/AC:L/PR:N) but a victim must click and authenticate (UI:R); open redirect yields limited credential/token exposure (C:L/I:L, A:N).
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Scoold is a Q&A and a knowledge sharing platform for teams. Prior to 1.69.1, the getBackToUrl() method in src/main/java/com/erudika/scoold/utils/HttpUtils.java validates the backto and returnto parameters with Strings.CI.startsWith against the configured server URL. An attacker can supply an absolute URL whose hostname begins with the legitimate hostname, causing URI.resolve() to retain the attacker URL and the prefix check to accept it. A victim who follows the crafted sign-in link can be redirected to an attacker-controlled domain after authentication, enabling phishing and possible credential or token theft. This issue is fixed in version 1.69.1.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Improper handling of Length parameter in GitHub repository erudika/scoold prior to 1.49.4. Rated high severity (CVSS 8.8
Scoold is a Q&A and a knowledge sharing platform for teams. Rated high severity (CVSS 8.7), this vulnerability is remote
Authentication bypass in Scoold prior to version 1.67.0 allows high-privileged attackers to inject arbitrary administrat
Scoold versions prior to 1.66.1 allow authenticated low-privilege users to delete any other user's feedback posts via an
Scoold versions prior to 1.66.2 allow authenticated low-privilege users to overwrite arbitrary existing questions by sub
Authentication bypass in Scoold (Erudika) prior to 1.69.1 allows an attacker who already possesses one of the server sig
Cross-origin request forgery in Erudika Scoold prior to 1.69.1 lets any attacker-controlled website issue credentialed A
EUVD-2026-102312
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB