{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52024 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52024 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52024 is a critical missing authorization vulnerability in n/a, published on 23 Jan 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-2025-52024 and fix it if it is affected.\n\nWhat it is: CVE-2025-52024 is a critical missing authorization vulnerability in n/a, published on 23 Jan 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-2025-52024 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2025-52024/ (Markdown: https://insights.sbomify.com/CVE-2025-52024/index.md)","id":"CVE-2025-52024","markdown":"https://insights.sbomify.com/CVE-2025-52024/index.md","name":"CVE-2025-52024","record":{"aliases":["GHSA-hcr4-42v2-c272"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"POS Platform Web Services","requires_auth":"none","summary":"Unauthenticated attackers can access internal API testing tools to discover and execute critical POS functions like transaction retrieval and credit adjustments.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gemscms_backend","vendor":"aptsys"}],"cvss":{"score":9.4,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-425","name":"Direct Request"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"A vulnerability exists in the Aptsys POS Platform Web Services module thru 2025-05-28, which exposes internal API testing tools to unauthenticated users. By accessing specific URLs, an attacker is presented with a directory-style index listing all available backend services and POS web services, each with an HTML form for submitting test input. These panels are intended for developer use, but are accessible in production environments with no authentication or session validation. This grants any external actor the ability to discover, test, and execute API endpoints that perform critical functions including but not limited to user transaction retrieval, credit adjustments, POS actions, and internal data queries.","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":"Missing authorization in n/a","id":"CVE-2025-52024","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-52025"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-52023"},"products":["n/a"],"published":"2026-01-23","related":[{"cvss_score":9.4,"headline":"SQL injection in n/a","id":"CVE-2025-52025","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2025-52026","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2025-52022","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2025-52023","kev_date_added":null,"published":"2026-01-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-07-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can access internal API testing tools to discover and execute critical POS functions like transaction retrieval and credit adjustments.","url":"https://insights.sbomify.com/CVE-2025-52024/"}