LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22211: SQL Injection in 74cms 3.2.0 via the key parameter to plus/ajax_street.php.

SQL Injection in 74cms 3.2.0 via the key parameter to plus/ajax_street.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-22211 reports SQL injection in 74cms 3.2.0 through the key parameter in plus/ajax_street.php. If an affected site is exposed, the business concern is possible database compromise. The public bundle does not provide CVSS, vendor patch details, or evidence of active exploitation.

Executive priority

Prioritize investigation if 74cms 3.2.0 is externally reachable. The issue type can affect sensitive data, but the public evidence is sparse and does not confirm exploitation or a patch path.

Technical view

The CVE description identifies a SQL injection issue in 74cms 3.2.0, specifically the key parameter handled by plus/ajax_street.php. No CWE, CVSS vector, fixed version, or vendor advisory is included in the provided sources. KEV status is false, so active exploitation is not established here.

Likely exposure

Exposure is most likely limited to organizations running 74cms 3.2.0 with plus/ajax_street.php reachable by untrusted users. The supplied affected-product metadata is incomplete, so confirm actual deployments rather than relying on CPE data.

Exploitation context

The sources describe the vulnerable parameter and endpoint but do not show reliable evidence of exploitation in the wild. This CVE is not listed as KEV in the provided bundle. Treat public-facing instances as higher concern until vendor guidance and logs are reviewed.

Researcher notes

The CVE record is minimal: affected metadata is not normalized, severity is absent, and the main technical reference is a GitHub issue. Validate against source code and deployment context before assigning urgency beyond the SQL injection class.

Mitigation direction

  • Identify whether any internet-facing systems run 74cms 3.2.0.
  • Check vendor or maintainer guidance for a fixed version or official workaround.
  • Restrict public access to affected 74cms administrative or dynamic endpoints where feasible.
  • Apply compensating controls for SQL injection detection at the web layer.
  • Prioritize database backups and least-privilege database accounts for exposed deployments.

Validation and detection

  • Inventory web assets for 74cms and confirm exact version numbers.
  • Verify whether plus/ajax_street.php is reachable from untrusted networks.
  • Review application logs for unusual requests targeting plus/ajax_street.php.
  • Confirm whether the key parameter is handled safely in the deployed code.
  • Document whether a vendor patch or workaround exists for your build.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2020-22211 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.