{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120555 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-120555 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-120555 is a medium-severity vulnerability in artbees Jupiter X Core, published on 7 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-120555 and fix it if it is affected.\n\nWhat it is: CVE-2026-120555 is a medium-severity vulnerability in artbees Jupiter X Core, published on 7 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-120555 in the wild and no public exploit code.\n\nAffected product: artbees Jupiter X Core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-120555/ (Markdown: https://insights.sbomify.com/CVE-2026-120555/index.md)","id":"CVE-2026-120555","markdown":"https://insights.sbomify.com/CVE-2026-120555/index.md","name":"CVE-2026-120555","record":{"aliases":["GHSA-p3jv-9gww-63p2"],"analysis":null,"analysis_generated_by":null,"assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Jupiter X Core plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.62.0 via the 'file' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. The path confinement check introduced in the CVE-2023-3813 fix (strpos + realpath) is present and working, so reads are confined to wp-content/uploads/ and cannot reach wp-config.php or other files outside that directory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Jupiter X Core \u003c= 4.62.0 - Missing Authorization to Unauthenticated Limited File Download via 'file' Parameter","id":"CVE-2026-120555","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"The Advanced Shipment Tracking for WooCommerce plugin for WordPress is vulnerable to SQL Injection via the `tracking_provider` parameter of","id":"CVE-2026-120558"},"nickname":null,"packages":[],"prev":{"headline":"The Import and export users and customers plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2","id":"CVE-2026-120554"},"products":["Jupiter X Core"],"published":"2026-11-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-08","vendors":["artbees"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-120555/"}