Security readout for executives and security teams
Plain-English summary
Listing Hub CMS 1.0 has an unauthenticated SQL injection in the pages.php id parameter. A remote attacker could query the backend database and expose sensitive data. Public exploit information exists, but the provided sources do not show confirmed active exploitation or a vendor patch.
Executive priority
Treat this as a near-term remediation item for any public Listing Hub CMS 1.0 site. The business risk is unauthorized database access, including possible credential and user data exposure. Prioritize discovery first, then vendor-guided upgrade, isolation, or removal.
Technical view
CVE-2019-25730 is CWE-89 SQL injection affecting Themerig Listing Hub CMS 1.0. The advisory describes crafted GET requests to pages.php using the id parameter to run arbitrary SQL queries. Reported impact includes extracting database credentials, usernames, and version information. CVSS 4.0 score is 8.8, network exploitable, low complexity, no privileges, no user interaction.
Likely exposure
Highest exposure is internet-facing Listing Hub CMS 1.0 installations, especially sites allowing public access to pages.php. Organizations using this product for directory or listings websites should assume the database tier may be reachable through the vulnerable web path until validated.
Exploitation context
ExploitDB is cited as an exploit reference, so public technical details exist. The source bundle marks CISA KEV as false and provides no evidence of active exploitation. Risk remains high because exploitation is unauthenticated, network-accessible, and targets database confidentiality.
Researcher notes
Sources identify Listing Hub CMS 1.0 only; do not broaden scope without product evidence. Public exploit material exists, but active exploitation is not established in the bundle. Patch status is unclear from provided sources, so remediation should reference vendor or marketplace guidance rather than assumed fixed versions.
Mitigation direction
- Identify any Listing Hub CMS 1.0 deployments and owners.
- Check Themerig, marketplace, and VulnCheck guidance for an official fix or upgrade path.
- If no fix is available, remove or isolate affected public instances.
- Restrict public access to vulnerable pages where business operations allow.
- Review web application firewall rules for SQL injection detection and blocking.
- Back up affected systems before any upgrade or configuration change.
Validation and detection
- Inventory web assets for Listing Hub CMS and version 1.0 indicators.
- Confirm whether pages.php is publicly reachable on affected sites.
- Review application logs for unusual id parameter database errors or probing.
- Check database logs for unexpected queries from the web application account.
- Validate remediation by confirming the vulnerable version or exposure is removed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-25730 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: 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
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-46419CVE reference, VulnCheck · exploit
- Official Product HomepageCVE reference, VulnCheck · product
- Official Product HomepageCVE reference, VulnCheck · product
- Product ReferenceCVE reference, VulnCheck · product
- VulnCheck Advisory: Listing Hub CMS 1.0 SQL Injection via pages.php idCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.