# CVE-2025-15498: SQL Injection in Pro3W CMS

> Unauthenticated attackers can bypass login via SQL injection to gain administrative privileges in Pro3W CMS.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/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:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-66jp-xvmj-6q6f

## What is CVE-2025-15498?

CVE-2025-15498 is a critical SQL injection vulnerability in Pro3W CMS, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pro3W CMS if vulnerable to SQL injection attacks. Improper neutralization of input provided into a login form allows an unauthenticated attacker to bypass authentication and gain administrative privileges. 

This issue was identified in version 1.2.0 of this software. Due to lack of response from the vendor exact version range could not be determined, but the vulnerability should be eliminated in versions released in January 2026 and later.

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

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


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

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

## Is CVE-2025-15498 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15498 is a critical SQL injection vulnerability in Pro3W CMS, published on 27 Feb 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-15498 in the wild and no public exploit code.

Affected product: Pro3W CMS. 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-15498/ (Markdown: https://insights.sbomify.com/CVE-2025-15498/index.md)
```

## Sources

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

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