{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52026 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52026 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52026 is a high-severity 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-52026 and fix it if it is affected.\n\nWhat it is: CVE-2025-52026 is a high-severity 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-52026 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-52026/ (Markdown: https://insights.sbomify.com/CVE-2025-52026/index.md)","id":"CVE-2025-52026","markdown":"https://insights.sbomify.com/CVE-2025-52026/index.md","name":"CVE-2025-52026","record":{"aliases":["GHSA-wfx8-p4c3-pcqp"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Aptsys gemscms backend","requires_auth":"none","summary":"Unauthenticated access to a backend endpoint exposes MD5-hashed cashier credentials, allowing attackers to reverse hashes and gain unauthorized access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gemscms_backend","vendor":"aptsys"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.","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":"Information disclosure in n/a","id":"CVE-2025-52026","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-52035"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-52025"},"products":["n/a"],"published":"2026-01-23","related":[{"cvss_score":9.4,"headline":"Missing authorization in n/a","id":"CVE-2025-52024","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":9.4,"headline":"SQL injection in n/a","id":"CVE-2025-52025","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 access to a backend endpoint exposes MD5-hashed cashier credentials, allowing attackers to reverse hashes and gain unauthorized access.","url":"https://insights.sbomify.com/CVE-2025-52026/"}