# CVE-2018-25300: XATABoost CMS 1.0.0 SQL Injection via news.php

> Unauthenticated attackers can extract sensitive database information via SQL injection in the news.php id parameter of XATABoost CMS.

- **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:** 29 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-8w85-j87r-r3qm

## What is CVE-2018-25300?

CVE-2018-25300 is a high-severity SQL injection vulnerability in XATABoost CMS, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XATABoost CMS 1.0.0 contains a union-based SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the id parameter. Attackers can send GET requests to news.php with malicious id values to extract sensitive database information.

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

## Which versions are affected by CVE-2018-25300?


## How do I fix CVE-2018-25300?

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

## Is CVE-2018-25300 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25300 and fix it if it is affected.

What it is: CVE-2018-25300 is a high-severity SQL injection vulnerability in XATABoost CMS, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25300 exists.

Affected product: XATABoost 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-2018-25300/ (Markdown: https://insights.sbomify.com/CVE-2018-25300/index.md)
```

## Sources

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

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