# CVE-2025-52392: Soosyze CMS's /user/login endpoint missing rate-limiting and lockout mechanisms

> Attackers can brute-force login attempts on Soosyze CMS due to missing rate-limiting, potentially gaining unauthorized administrative access.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Aug 2025
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-vq9x-w82r-rhmc

## What is CVE-2025-52392?

CVE-2025-52392 is a medium-severity authentication bypass vulnerability in n/a, published on 13 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Soosyze CMS 2.0 allows brute-force login attacks via the /user/login endpoint due to missing rate-limiting and lockout mechanisms. An attacker can repeatedly submit login attempts without restrictions, potentially gaining unauthorized administrative access. This vulnerability corresponds to CWE-307: Improper Restriction of Excessive Authentication Attempts.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

2 open source packages ship an affected version, including soosyze/soosyze.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `soosyze/soosyze` | Packagist | All versions to 2.0.0 | None |
| `soosyze/soosyze` | Packagist | All versions to 2.0.0 | None |

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

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

## Is CVE-2025-52392 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52392 exists.

Public exploit code:

- Soosyze CMS 2.0 - Brute Force Login (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52392 is a medium-severity authentication bypass vulnerability in n/a, published on 13 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52392 exists.

Affected packages and fixed versions:
- soosyze/soosyze (Packagist): affected all versions up to 2.0.0; no fix listed
- soosyze/soosyze (Packagist): affected all versions up to 2.0.0; no fix listed

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-52392/ (Markdown: https://insights.sbomify.com/CVE-2025-52392/index.md)
```

## Sources

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

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