# CVE-2026-124575: SiteServer SSCMS Admin-Login CAPTCHA LoginController.Submit.cs LoginController.Submit excessive authentication


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-v7j8-qp7g-hgm2

## What is CVE-2026-124575?

CVE-2026-124575 is a medium-severity vulnerability in SiteServer SSCMS, published on 9 Nov 2026. 

### Official description

A vulnerability was identified in SiteServer SSCMS up to 7.1.3/7.2.1/7.4.0. This issue affects the function LoginController.Submit of the file src/SSCMS.Web/Controllers/Admin/LoginController.Submit.cs of the component Admin-Login CAPTCHA. Such manipulation of the argument isForceLogoutAndLogin leads to improper restriction of excessive authentication attempts. It is possible to launch the attack remotely. A high complexity level is associated with this attack. The exploitability is assessed as difficult. The name of the patch is df3becb7ebb00a48435418a44fd08a459eb38ace. Applying a patch is advised to resolve this issue.

Weakness: CWE-799 (Improper Control of Interaction Frequency), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-124575?


## How do I fix CVE-2026-124575?

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

## Is CVE-2026-124575 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124575 and fix it if it is affected.

What it is: CVE-2026-124575 is a medium-severity vulnerability in SiteServer SSCMS, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124575 in the wild and no public exploit code.

Affected product: SiteServer SSCMS. 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-2026-124575/ (Markdown: https://insights.sbomify.com/CVE-2026-124575/index.md)
```

## Sources

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

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