SQL Injection in XATABoost CMS 1.0.0 news.php id Parameter
CVE-2018-25300 is a union-based SQL injection vulnerability in XATABoost CMS 1.0.0. The flaw is present in the id parameter processed by news.php. An attacker can send crafted GET requests with malicious SQL syntax in the id parameter, causing the application to concatenate or otherwise use untrusted input in backend database queries. The issue is exploitable remotely without authentication and enables manipulation of SQL query logic, including UNION-based extraction of data from the underlying database.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows unauthenticated remote attackers to manipulate database queries and extract sensitive database information. Based on the provided CVSS context, the primary impact is high confidentiality loss, with limited integrity impact and no stated availability impact.
If you can’t patch tonight, do this now.
If an official fix is not available, restrict external access to the affected application, especially news.php, through network controls, reverse proxy rules, or WAF filtering for SQL injection patterns. Enforce strict allowlisting for numeric id values at the application or web server layer, monitor logs for suspicious crafted GET requests to news.php, and minimize database account privileges used by the CMS to reduce exposure of sensitive data.
Patch, then assume compromise.
Upgrade XATABoost CMS to a fixed version if one is available from the vendor. In the affected code path, eliminate dynamic SQL construction using untrusted input from the id parameter in news.php. Use parameterized queries or prepared statements, enforce strict server-side input validation and type checking for id, and review similar request parameters across the application for the same flaw pattern.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.