# CVE-2025-52024: Missing authorization in n/a

> Unauthenticated attackers can access internal API testing tools to discover and execute critical POS functions like transaction retrieval and credit adjustments.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-hcr4-42v2-c272

## What is CVE-2025-52024?

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.

### Official 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.

Weakness: CWE-862 (Missing Authorization), CWE-425 (Direct Request), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-52024?

It affects 1 product.


Products: Aptsys Gemscms Backend.

## How do I fix CVE-2025-52024?

No fix has been published for CVE-2025-52024 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52024 being exploited?

There is no known exploitation of CVE-2025-52024 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-52025](https://insights.sbomify.com/CVE-2025-52025/): SQL injection in n/a (critical 9.4)
- [CVE-2025-52026](https://insights.sbomify.com/CVE-2025-52026/): Information disclosure in n/a (high 7.5)
- [CVE-2025-52022](https://insights.sbomify.com/CVE-2025-52022/): Information disclosure in n/a (medium 5.3)
- [CVE-2025-52023](https://insights.sbomify.com/CVE-2025-52023/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52024 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2025-52024 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52024/ (Markdown: https://insights.sbomify.com/CVE-2025-52024/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52024
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52024
- OSV: https://osv.dev/vulnerability/CVE-2025-52024

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52024/
Summaries are generated and may contain mistakes; the official description above is the record.