{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-91078 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-91078 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-91078 is a high-severity vulnerability in Unknown TillKit, published on 3 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-91078 and fix it if it is affected.\n\nWhat it is: CVE-2026-91078 is a high-severity vulnerability in Unknown TillKit, published on 3 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-91078 in the wild and no public exploit code.\n\nAffected product: Unknown TillKit. 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-91078/ (Markdown: https://insights.sbomify.com/CVE-2026-91078/index.md)","id":"CVE-2026-91078","markdown":"https://insights.sbomify.com/CVE-2026-91078/index.md","name":"CVE-2026-91078","record":{"aliases":["GHSA-mhjv-47jj-mxpp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress POS plugin","requires_auth":"none","summary":"Unauthenticated attackers can use a hard-coded PIN to access the POS interface, allowing them to read customer data and modify store information.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The TillKit WordPress plugin before 1.0.5 does not require the hard-coded, publicly known PIN of the privileged POS account it creates on activation to be changed before use, and it authenticates its public POS login endpoint on that PIN alone with no identity or capability check, allowing unauthenticated attackers to obtain a privileged POS session and thereby read customer and site-user personal data and modify store data.","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":"TillKit \u003c 1.0.5 - Unauthenticated POS Takeover via Hard-Coded Default Manager PIN","id":"CVE-2026-91078","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Huly Platform through 0.7.426 SSRF via Print Service","id":"CVE-2026-91079"},"packages":[],"prev":{"headline":"Missing authorization in Event Booking Manager for WooCommerce","id":"CVE-2026-91077"},"products":["TillKit"],"published":"2026-10-03","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-10-03","vendors":["Unknown"]},"summary":"Unauthenticated attackers can use a hard-coded PIN to access the POS interface, allowing them to read customer data and modify store information.","url":"https://insights.sbomify.com/CVE-2026-91078/"}