CVE-2026-48518

MultiJuicer: Login CSRF allows attacker to force victims into their team

Published Jun 15, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
MultiJuicer is used to run separate Juice Shop instances on a central kubernetes cluster without the need for local instances. In versions 8.0.0 through 10.0.0, the team join endpoint (POST /multi-juicer/api/teams/{team}/join) accepted requests with any Content-Type, including text/plain. Because that content type does not trigger a CORS preflight, an attacker could host a cross-site HTML form that auto-submits to the endpoint and forces a victim's browser to log in as the attacker's team. A successful, undetected attacker can cause victims to unwittingly solve Juice Shop challenges under the attacker's team identity. In a CTF context this lets the attacker inflate their team's score using other players' activity, and any sensitive data the victim enters into "their" Juice Shop ends up in the attacker's instance. The vulnerability is exploitable without any prior authentication; the victim
only needs to visit a page the attacker controls while having network access to the MultiJuicer deployment. SameSite=Strict on the session cookie does not mitigate this, because the attack plants a new cookie rather than relying on an existing one. This issue was fixed in version 10.0.1.

Analysis

AI-generated

Technical impact

The vulnerability arises from the team join endpoint accepting any Content‑Type, including text/plain, which bypasses the sameSite cookie restriction and allows the attacker to auto‑submit a form that forces the victim's browser to authenticate to the attacker's team. This results in the victim unknowingly solving challenges under the attacker's identity and any sensitive data they submit to the Juice Shop instance being stored in the attacker's instance.

Affected Systems

Affected product: juice‑shop multi‑juicer, versions 8.0.0 through 10.0.0. The issue was fixed in version 10.0.1.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity; the EPSS score is less than 1%, suggesting low likelihood of exploitation. The vulnerability is exploit‑agnostic of authentication – an attacker simply hosts a malicious HTML form and lures a victim who has network access to the deployment to load the page. The attack is browser‑based and requires no special infrastructure. The vulnerability is not currently listed in the CISA KEV catalog.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update MultiJuicer to version 10.0.1 or later.
  • Configure the server to reject non‑JSON content types for the "/multi-juicer/api/teams/{team}/join" endpoint, allowing only application/json.
  • Restrict access to the join endpoint with network segmentation or firewall rules to trusted clients.

Generated by OpenCVE AI on June 18, 2026 at 01:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Juice-shop
Juice-shop multi-juicer
Vendors & Products Juice-shop
Juice-shop multi-juicer
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description MultiJuicer is used to run separate Juice Shop instances on a central kubernetes cluster without the need for local instances. In versions 8.0.0 through 10.0.0, the team join endpoint (POST /multi-juicer/api/teams/{team}/join) accepted requests with any Content-Type, including text/plain. Because that content type does not trigger a CORS preflight, an attacker could host a cross-site HTML form that auto-submits to the endpoint and forces a victim's browser to log in as the attacker's team. A successful, undetected attacker can cause victims to unwittingly solve Juice Shop challenges under the attacker's team identity. In a CTF context this lets the attacker inflate their team's score using other players' activity, and any sensitive data the victim enters into "their" Juice Shop ends up in the attacker's instance. The vulnerability is exploitable without any prior authentication; the victim only needs to visit a page the attacker controls while having network access to the MultiJuicer deployment. SameSite=Strict on the session cookie does not mitigate this, because the attack plants a new cookie rather than relying on an existing one. This issue was fixed in version 10.0.1.
Title MultiJuicer: Login CSRF allows attacker to force victims into their team
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jun 16, 2026, 12:36 PM
Reserved
May 21, 2026, 4:18 PM
Status
Deferred
Published
Jun 15, 2026, 9:17 PM
Modified
Oct 25, 2026, 11:10 PM