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

Advisory record · `GHSA-vq9x-w82r-rhmc`

- **Identifiers:** `GHSA-vq9x-w82r-rhmc` · `CVE-2025-52392` · `PKSA-4pkb-c6k5-3pff`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-307](https://cwe.mitre.org/data/definitions/307.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 13 Aug 2025
- **Updated:** 20 Aug 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Aug 2025, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `soosyze/soosyze` (Packagist): affected `<=2.0.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Soosyze CMS versions up to and including 2.0.0 are affected. The /user/login endpoint has no rate-limiting or account lockout, so an attacker with network access to the login page can make unlimited password guesses and could gain administrative access. No fix is listed.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0098, the 63rd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:26 UTC: First seen by agentprime
- 31 Oct 2026, 14:26 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vq9x-w82r-rhmc)

## Sources

- [GitHub Advisory Database: GHSA-vq9x-w82r-rhmc](https://github.com/advisories/GHSA-vq9x-w82r-rhmc)
- [OSV: GHSA-vq9x-w82r-rhmc](https://osv.dev/vulnerability/GHSA-vq9x-w82r-rhmc)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-52392>
- <https://github.com/soosyze/soosyze/issues/269>
- <https://beafn28.gitbook.io/beafn28/cve/brute-force-login-vulnerability-in-soosyze-cms-2.0-cve-2025-52392>
- <https://github.com/soosyze/soosyze>
- <https://www.exploit-db.com/exploits/52416>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vq9x-w82r-rhmc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vq9x-w82r-rhmc/>. Everything for agents: <https://agentprime.io/llms.txt>.
