Quick answers
- Is CVE-2026-48518 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48518 being exploited in the wild.
- How severe is CVE-2026-48518?
- Medium severity, with a CVSS score of 4.3, published 15 June 2026.
- Which products and versions are affected?
- OWASP MultiJuicer 8.0.0 - 10.0.0.
- Is there a fix for CVE-2026-48518?
- A patch was published on 2026-05-21: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48518 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48518?
- Check whether you run OWASP MultiJuicer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Cross-Site Request Forgery (CSRF) vulnerability exists in the MultiJuicer team join endpoint (POST /multi-juicer/api/teams/{team}/join). The endpoint fails to strictly validate the Content-Type header, accepting 'text/plain' requests which do not trigger a CORS preflight check in web browsers. An unauthenticated remote attacker can exploit this by hosting a malicious HTML form that auto-submits to the endpoint, forcing the victim's browser to establish a session under the attacker's team identity. This bypasses SameSite=Strict cookie protections because the attack plants a new session cookie rather than hijacking an existing one. The issue is resolved in version 10.0.1 by requiring the 'application/json' Content-Type for all JSON POST endpoints.
Affected products
- OWASP Juice Shop Project MultiJuicer 8.0.0 - 10.0.0
Timeline
- 2026-05-21: disclosed: Issue reported and fix suggested via GitHub issue #525
- 2026-05-21: patched: Fix committed to repository
- 2026-06-15: advisory: CVE-2026-48518 published