Security readout for executives and security teams
Plain-English summary
CVE-2017-11174 is a SQL injection issue in the XOOPS 2.5.8.1 Core installer database settings page. The business risk is mainly for sites where installation files remain reachable. Public sources do not provide CVSS scoring, confirmed exploitation, or a named fixed version in the supplied bundle.
Executive priority
Handle as a targeted legacy web application risk. It is not confirmed actively exploited in the supplied sources, but reachable installer code can create avoidable database compromise exposure. Prioritize if XOOPS 2.5.8.1 is internet-facing.
Technical view
The issue is in install/page_dbsettings.php. Unfiltered data reaches CREATE and ALTER SQL queries through CHARACTER SET and COLLATE handling, related to GBK use. The supplied affected scope is XOOPS Core 2.5.8.1 only; no CPE, CWE, CVSS, or patch detail is provided.
Likely exposure
Exposure is most likely on XOOPS 2.5.8.1 deployments where the installer or database settings page is present and web-accessible. Already-installed sites with installation files removed or inaccessible are less likely exposed, based on the vulnerable component location.
Exploitation context
The CVE is public and has a referenced technical blog. The supplied sources do not show CISA KEV listing, in-the-wild exploitation, weaponized tooling, or exploit prevalence. Treat exploitation status as unconfirmed.
Researcher notes
Evidence is sparse: the CVE record and referenced blog identify the vulnerable file and SQL query context, but the bundle lacks CVSS, CWE, CPE, fix commit, or official advisory details. Avoid expanding scope beyond XOOPS Core 2.5.8.1 without additional vendor evidence.
Mitigation direction
- Check XOOPS project guidance for a fixed or supported upgrade path.
- Remove or restrict access to installer files when installation is complete.
- Limit installer access to trusted administrative networks during setup.
- Review web server logs for unexpected installer page access.
- Prioritize replacement of unsupported XOOPS 2.5.8.1 deployments.
Validation and detection
- Inventory public sites running XOOPS Core 2.5.8.1.
- Confirm whether install/page_dbsettings.php is present and reachable.
- Review configuration management for retained installation directories.
- Check logs for requests to XOOPS installer paths.
- Document compensating controls if vendor guidance is unavailable.
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.
Database 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-2017-11174 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://tsublogs.wordpress.com/2017/07/12/xoops-core-2-5-8-1-install-db-sql-injection/CVE reference · x_refsource_MISC
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.
