Skip to main content
Vulnerability Database/CVE-2026-55842

CVE-2026-55842: Scoold Q&A Platform CSRF Vulnerability

CVE-2026-55842 is a cross-site request forgery vulnerability in Scoold Q&A platform that allows malicious sites to perform authenticated API requests on behalf of logged-in users. This article covers technical details, affected versions, and mitigation steps.

Published:

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-55842 Overview

Scoold, an open-source Q&A and knowledge sharing platform for teams developed by Erudika, contains a Cross-Origin Resource Sharing (CORS) misconfiguration in versions prior to 1.69.1. The apiCorsConfiguration() method in src/main/java/com/erudika/scoold/ScooldServer.java combines addAllowedOriginPattern("*") with setAllowCredentials(true). This configuration causes Spring to reflect any requesting origin while still permitting cookies and session tokens. A malicious website visited by a logged-in Scoold user can issue authenticated API requests, read user data, and trigger state-changing operations on the victim's behalf. The issue is tracked as [CWE-346: Origin Validation Error] and resolved in version 1.69.1.

Critical Impact

Authenticated Scoold users who visit attacker-controlled websites can have their sessions abused to read private data and perform state-changing actions on the Scoold instance.

Affected Products

  • Scoold versions prior to 1.69.1
  • Deployments with the API endpoint and CORS enabled
  • Any Scoold instance using the default apiCorsConfiguration() method

Discovery Timeline

  • 2026-10-15 - CVE-2026-55842 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-55842

Vulnerability Analysis

The vulnerability resides in Scoold's Spring Security CORS configuration. The apiCorsConfiguration() method registers a wildcard origin pattern using cors.addAllowedOriginPattern("*") while simultaneously allowing credentials via setAllowCredentials(true). Spring handles this combination by reflecting the exact Origin header of the incoming request back in the Access-Control-Allow-Origin response header. Browsers therefore treat any origin as trusted and transmit the user's session cookies with cross-origin requests.

This effectively nullifies the Same-Origin Policy for Scoold's API endpoints. An attacker-controlled page can read JSON responses that would otherwise be shielded by the browser's cross-origin protections.

Root Cause

The root cause is an insecure combination of two Spring CORS settings. addAllowedOriginPattern("*") was intended to support flexible origin matching, but when paired with credentialed requests it reflects every origin without validation. The Scoold code lacked an allow-list of trusted origins and did not restrict credentialed requests to the server's own URL.

Attack Vector

Exploitation requires a logged-in Scoold user to visit a malicious page. The page issues fetch() or XMLHttpRequest calls to the target Scoold instance with credentials: 'include'. Because the server echoes the attacker's origin and permits credentials, the browser attaches the user's session cookie. The attacker can then read responses containing user data, questions, and configuration, or trigger write operations through authenticated API calls.

java
	private CorsConfiguration apiCorsConfiguration() {
		CorsConfiguration cors = new CorsConfiguration();
-		cors.addAllowedOriginPattern("*");
+		String origins = CONF.corsAllowedOrigins();
+		if (!StringUtils.isBlank(origins)) {
+			cors.setAllowedOrigins(Arrays.stream(origins.split("\\s*,\\s*")).filter(StringUtils::isNotBlank).distinct().toList());
+		} else {
+			cors.addAllowedOrigin(CONF.serverUrl());
+		}
		cors.addAllowedMethod("*");
		cors.addAllowedHeader("*");
		cors.setExposedHeaders(Arrays.asList("Mcp-Protocol-Version", "Mcp-Session-Id"));

Source: GitHub Commit 6412441. The patch replaces the wildcard pattern with either an administrator-defined allow-list from the new cors_allowed_origins configuration parameter or the server's own URL as a fallback.

Detection Methods for CVE-2026-55842

Indicators of Compromise

  • API access logs containing authenticated requests where the Referer or Origin header points to an untrusted third-party domain.
  • Access-Control-Allow-Origin response headers echoing arbitrary external origins alongside Access-Control-Allow-Credentials: true.
  • Unexpected state-changing API calls (post, vote, profile edit) that correlate with user web browsing timestamps rather than typical Scoold UI usage.

Detection Strategies

  • Inspect running Scoold instances for the vulnerable version string and check the apiCorsConfiguration() source if the deployment is customized.
  • Replay a benign request from a non-Scoold origin and verify whether the server reflects that origin in the CORS response headers.
  • Review web proxy logs for cross-origin preflight (OPTIONS) requests directed at /api/* paths originating from unexpected referrers.

Monitoring Recommendations

  • Alert on HTTP responses where Access-Control-Allow-Origin is dynamic and Access-Control-Allow-Credentials is true on sensitive endpoints.
  • Correlate authenticated API events with session-origin IP addresses and user-agent patterns to spot CSRF-like abuse.
  • Monitor outbound requests from corporate browsers to the Scoold API for fetch calls with uncommon origin headers.

How to Mitigate CVE-2026-55842

Immediate Actions Required

  • Upgrade Scoold to version 1.69.1 or later as published in the GitHub Release 1.69.1.
  • Configure the new cors_allowed_origins setting with an explicit list of trusted origins for your deployment.
  • Invalidate active user sessions after upgrade to force reauthentication from a clean state.

Patch Information

The fix is delivered in Scoold 1.69.1. The patch adds a corsAllowedOrigins() configuration parameter and replaces addAllowedOriginPattern("*") with either the administrator-defined allow-list or the server's own URL. Full technical detail is available in the GitHub Security Advisory GHSA-q684-4jqv-c63c.

Workarounds

  • Disable the CORS feature by setting cors_enabled=false if your deployment does not require cross-origin API access.
  • Place Scoold behind a reverse proxy (nginx, Apache, or a Web Application Firewall) that strips or overrides reflected Access-Control-Allow-Origin headers with a strict allow-list.
  • Restrict API access to internal networks only, preventing attacker-controlled browsers from reaching the vulnerable endpoints.
bash
# Configuration example for Scoold 1.69.1+
# Set an explicit allow-list of trusted origins in application.conf
scoold.cors_enabled = true
scoold.cors_allowed_origins = "https://scoold.example.com,https://portal.example.com"

# Or leave empty to allow only the server's own origin
scoold.cors_allowed_origins = ""

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.