Security readout for executives and security teams
Plain-English summary
CVE-2018-19558 is a reported SQL injection issue in arcms through 2018-03-19. If the affected endpoint is exposed, attacker-supplied input may influence database queries. The bundle does not provide CVSS, affected CPEs, a named patch, or active exploitation evidence.
Executive priority
Prioritize confirmation of whether arcms is used and externally exposed. Business urgency is uncertain because severity and exploitation evidence are missing, but SQL injection can threaten application data.
Technical view
The CVE states SQL injection exists through the json/newslist limit parameter, tied to ctl/main/Json.php, ctl/main/service/Data.php, and comp/Db/Mysql.php. The record lists no CVSS score, CWE, CPE, vendor advisory, or confirmed fixed version.
Likely exposure
Exposure is limited to organizations running arcms through 2018-03-19 with the json/newslist functionality reachable. The CVE record’s affected product metadata is n/a, so asset owners must confirm usage directly.
Exploitation context
The issue has a public GitHub reference, but the source bundle does not show KEV inclusion or cited evidence of active exploitation. Treat exploit status as unconfirmed.
Researcher notes
Evidence is sparse. The key claim is parameter-level SQL injection in json/newslist limit. Avoid assuming affected versions beyond “through 2018-03-19,” exploit availability, or a patch unless the project reference confirms it.
Mitigation direction
- Check the arcms project issue and vendor guidance for any corrected release or recommended workaround.
- Restrict public access to json/newslist if the functionality is not required externally.
- Retire or replace arcms deployments if no maintained fixed version is available.
- Use least-privilege database accounts for the application.
- Monitor application and database logs for suspicious json/newslist activity.
Validation and detection
- Inventory any arcms deployments and confirm whether they are through 2018-03-19.
- Confirm whether json/newslist is reachable from untrusted networks.
- Review application code for the referenced files and unsafe limit handling.
- Check web and database logs for unusual requests to json/newslist.
- Verify any remediation against vendor or project guidance before closing.
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-2018-19558 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://github.com/assnr/arcms/issues/1CVE 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.