# CVE-2019-25539: 202CMS v10 beta SQL Injection via register.php

> Unauthenticated attackers can extract sensitive database information via blind SQL injection in 202CMS.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-wv3m-9xj9-vcq2

## What is CVE-2019-25539?

CVE-2019-25539 is a high-severity SQL injection vulnerability in Sourceforge 202CMS, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

202CMS v10 beta contains a blind SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the log_user parameter. Attackers can send POST requests to index.php with crafted SQL payloads using time-based blind injection techniques to extract sensitive database information.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-25539?

It affects 1 product.


Products: Konradpl99 202cms.

## How do I fix CVE-2019-25539?

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

## Is CVE-2019-25539 being exploited?

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

## Other vulnerabilities in Sourceforge 202CMS

- [CVE-2019-25538](https://insights.sbomify.com/CVE-2019-25538/): 202CMS v10 beta SQL Injection via log_user Parameter (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25539 and fix it if it is affected.

What it is: CVE-2019-25539 is a high-severity SQL injection vulnerability in Sourceforge 202CMS, published on 12 Mar 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-2019-25539 in the wild and no public exploit code.

Affected product: Sourceforge 202CMS. 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-2019-25539/ (Markdown: https://insights.sbomify.com/CVE-2019-25539/index.md)
```

## Sources

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

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