Unauthenticated database disclosure via injectable pages.php id
Published Jun 4, 2026 · Updated Jun 4, 2026
SQL injection in Listing Hub CMS 1.0 allows remote attackers to read database contents through the id parameter of pages.php. The request reaches a PDO query in includes/head.php that treats crafted id content as SQL, and database errors return query results. No authentication or user interaction is required; the demonstrated payload exposes the database user, database name, and server version.
Summary
What happened
SQL injection in Listing Hub CMS 1.0 allows remote attackers to read database contents through the id parameter of pages.php. The request reaches a PDO query in includes/head.php that treats crafted id content as SQL, and database errors return query results. No authentication or user interaction is required; the demonstrated payload exposes the database user, database name, and server version.
The record
- CVE
- CVE-2019-25730
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Themerig
- Product
- Listing Hub CMS
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Listing Hub CMS 1.0 pages.php id SQL Injectionfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo