Security readout for executives and security teams
Plain-English summary
CVE-2020-22199 is a reported SQL injection issue in phpCMS 2007 SP6 build 0805. The vulnerable input is described as the digg_mod parameter in digg_add.php. Business urgency depends on whether this very old phpCMS version is still deployed and reachable.
Executive priority
Prioritize inventory first. If the affected legacy phpCMS build is internet-facing, treat remediation as urgent because SQL injection can threaten site data and integrity. If not present, record non-exposure and monitor vendor guidance.
Technical view
The CVE record describes SQL injection through digg_mod in digg_add.php for phpCMS 2007 SP6 build 0805. The source bundle provides no CVSS score, CWE mapping, confirmed patch, or detailed affected CPE data. KEV status is false.
Likely exposure
Likely exposure is limited to organizations still running phpCMS 2007 SP6 build 0805 with digg_add.php accessible. The affected metadata in the record is incomplete, so product inventory confirmation is essential before assigning risk.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. The referenced public issue indicates the vulnerability report, but the bundle does not provide exploit prevalence, maturity, or attacker use evidence.
Researcher notes
Evidence is sparse. The CVE record names the vulnerable parameter and file but lacks CVSS, CWE, CPEs, patch details, and exploitation evidence. Do not broaden scope beyond phpCMS 2007 SP6 build 0805 without independent confirmation.
Mitigation direction
- Identify any phpCMS 2007 SP6 build 0805 deployments.
- Check phpCMS or project guidance for supported fixes or replacements.
- Restrict public access to affected phpCMS paths where possible.
- Retire or migrate unsupported legacy phpCMS installations.
- Review database and application logs for suspicious access patterns.
Validation and detection
- Search asset inventory for phpCMS 2007 SP6 build 0805.
- Confirm whether digg_add.php is present and reachable.
- Check web logs for requests involving digg_add.php or digg_mod.
- Verify any compensating access controls block untrusted access.
- Document whether the application is still business required.
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-2020-22199 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/blindkey/cve_like/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.