FKIE_CVE-2026-48518

Vulnerability from fkie_nvd - Published: 2026-06-15 21:17 - Updated: 2026-06-17 10:55
Severity
4.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Summary
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.
References
security-advisories@github.comhttps://github.com/juice-shop/multi-juicer/commit/75b08c3fdda410781d421bfdf041fb1e913d6b49
security-advisories@github.comhttps://github.com/juice-shop/multi-juicer/issues/525
security-advisories@github.comhttps://github.com/juice-shop/multi-juicer/security/advisories/GHSA-h759-hf7w-j6m6
134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/juice-shop/multi-juicer/security/advisories/GHSA-h759-hf7w-j6m6
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "multi-juicer",
          "vendor": "juice-shop",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 8.0.0, \u003c 10.0.1"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u0027s browser to log in as the attacker\u0027s team. A successful, undetected attacker can cause victims to unwittingly solve Juice Shop challenges under the attacker\u0027s team identity. In a CTF context this lets the attacker inflate their team\u0027s score using other players\u0027 activity, and any sensitive data the victim enters into \"their\" Juice Shop ends up in the attacker\u0027s instance. The vulnerability is exploitable without any prior authentication; the victim\nonly 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."
    }
  ],
  "id": "CVE-2026-48518",
  "lastModified": "2026-06-17T10:55:03.403",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 4.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 1.4,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-48518",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-06-16T12:36:02.554673Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-06-15T21:17:14.057",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/juice-shop/multi-juicer/commit/75b08c3fdda410781d421bfdf041fb1e913d6b49"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/juice-shop/multi-juicer/issues/525"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/juice-shop/multi-juicer/security/advisories/GHSA-h759-hf7w-j6m6"
    },
    {
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "url": "https://github.com/juice-shop/multi-juicer/security/advisories/GHSA-h759-hf7w-j6m6"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-352"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.