CVE-2026-48518: MultiJuicer CSRF Vulnerability Allows Team Hijacking and Score Inflation

Technical summary

The vulnerability stems from improper content-type handling on the POST /multi-juicer/api/teams/{team}/join endpoint. The endpoint fails to enforce strict content-type validation, accepting text/plain alongside application/json. Browser CORS preflight checks only trigger for certain content types; text/plain does not require a preflight request, allowing attackers to craft simple HTML forms that auto-submit cross-origin requests. Because the endpoint creates a new session cookie via successful login rather than relying on transmission of an existing authenticated session, SameSite=Strict protections offer no defense. Affected versions 8.0.0 through 10.0.1 lack proper CSRF token validation or stricter content-type requirements. The fix in 10.0.1 implements proper CSRF protections and content-type enforcement.

Business impact

In competitive CTF (Capture The Flag) and security training environments, this vulnerability enables score manipulation and unfair competition. Attackers can harvest victims' challenge solutions to inflate team rankings. More critically, any sensitive test data, passwords, or information victims enter into their Juice Shop instance is logged under the attacker's team account, creating a data exfiltration vector. Organizations using MultiJuicer for authorized security training and assessment face compromised exercise integrity, inaccurate performance metrics, and potential exposure of training data to unauthorized parties.

Affected systems

MultiJuicer versions 8.0.0 through 10.0.0 are vulnerable. Version 10.0.1 and later include the fix. Any MultiJuicer deployment exposed to untrusted network sources or accessible from the public internet is at risk. The vulnerability affects deployments regardless of whether they run local or remote Juice Shop instances, as the flaw exists in MultiJuicer's team management endpoint itself.

Exploitability

This vulnerability is straightforward to exploit. An attacker requires only the ability to host a simple web page (or inject HTML into a page the victim visits) and knowledge of the MultiJuicer deployment URL. No authentication is required, no user interaction beyond visiting a malicious page is needed, and exploit code is trivial—a single auto-submitting HTML form suffices. The attack succeeds as long as the victim's browser has network access to the MultiJuicer instance. The CVSS score of 4.3 (MEDIUM) reflects low confidentiality impact but recognizes the ease of exploitation and lack of authentication barriers.

Remediation

Upgrade to MultiJuicer version 10.0.1 or later immediately. This release implements CSRF token validation on the team join endpoint and enforces strict content-type checking, blocking requests that do not match expected types. For organizations unable to upgrade immediately, restrict network access to the MultiJuicer deployment to trusted networks only, implement a Web Application Firewall (WAF) rule to block POST requests to /multi-juicer/api/teams/*/join from unexpected sources, and educate users not to visit untrusted URLs while accessing MultiJuicer.

Patch guidance

Apply MultiJuicer version 10.0.1 or any subsequent release as part of your next maintenance window. The patch is a minor version bump and should not introduce breaking changes. Verify patch application by confirming the version number via your deployment's management interface or logs. Test the team join functionality in a non-production environment before rolling out to production to confirm normal workflow remains intact.

Detection guidance

Monitor application logs for unusual patterns on the team join endpoint, such as multiple rapid join requests from different IP addresses or browsers, or join requests originating from unexpected referrer headers. Network-based detection can flag POST requests to /multi-juicer/api/teams/*/join with text/plain or missing content-type headers. Review team membership activity for anomalies—sudden enrollment of legitimate users into unfamiliar teams may indicate exploitation. Correlate MultiJuicer join logs with web proxy or firewall logs to identify visits to external sites from users shortly before unwanted team enrollment.

Why prioritize this

Although the CVSS score is MEDIUM (4.3), this vulnerability warrants prompt attention in any CTF or authorized security training context. The attack is trivially simple, requires zero authentication, and directly undermines the integrity of exercises and fair competition. The business impact—score inflation and data exposure—is concrete and measurable. Organizations running public or semi-public MultiJuicer instances should treat this as high priority. Deployments isolated to trusted networks face lower risk but should still patch within a standard update cycle.

Risk score, explained

The CVSS 3.1 score of 4.3 reflects MEDIUM severity. The attack vector is network-based and requires low complexity, with no privileges needed (PR:N). However, user interaction is required (UI:R), as the victim must visit the attacker's page. Integrity impact (I:L) is acknowledged—the attacker can enroll victims in teams and claim their work—but confidentiality and availability remain unaffected. The score appropriately captures that while exploitation is easy, the impact is contained to integrity of team identity and challenge attribution rather than system compromise or data breach.

Frequently asked questions