LiveActive security incident?Get immediate response
CVE Record

CVE-2020-13567: Multiple SQL injection vulnerabilities exist in phpGACL 3.3.7.

Multiple SQL injection vulnerabilities exist in phpGACL 3.3.7. A specially crafted HTTP request can lead to a SQL injection. An attacker can send an HTTP request to trigger this vulnerability.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes multiple SQL injection flaws in phpGACL 3.3.7, with OpenEMR 5.0.2 and a 6.0.0 development commit listed as affected. A logged-in attacker could send crafted web requests that may compromise sensitive data, change records, or disrupt service.

Executive priority

Treat as a high-priority remediation item for healthcare or identity-sensitive environments. It is not listed as actively exploited in the supplied evidence, but potential database compromise makes exposure reduction and vendor-guided remediation urgent.

Technical view

The CVSS 3.0 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating network reachability, low attack complexity, low privileges required, and high confidentiality, integrity, and availability impact. The weakness is CWE-89 SQL injection. Sources do not provide patch details in the supplied bundle.

Likely exposure

Exposure is most likely where phpGACL 3.3.7 is deployed directly or through the listed OpenEMR versions: 5.0.2 or the named 6.0.0 development commit. Internet-facing authenticated web access increases business risk.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability still matters because the CVSS vector indicates a low-privileged authenticated attacker can trigger SQL injection remotely without user interaction.

Researcher notes

The public bundle identifies SQL injection, affected versions, CWE-89, and CVSS impact, but does not include safe validation details or a named fix. Avoid assuming exploit availability or remediation specifics beyond vendor guidance.

Mitigation direction

  • Inventory phpGACL and OpenEMR deployments for the affected versions listed in the CVE bundle.
  • Check phpGACL and OpenEMR vendor guidance for supported fixes or upgrade paths.
  • Restrict access to affected web interfaces using network controls and least-privilege accounts.
  • Review application and database logs for unusual authenticated requests or SQL error patterns.
  • Prioritize migration away from unsupported affected builds if vendor support is unavailable.

Validation and detection

  • Confirm installed phpGACL and OpenEMR versions against the affected list.
  • Verify whether the deployment includes phpGACL 3.3.7 components.
  • Check whether affected interfaces are reachable from untrusted networks.
  • Review user roles with access to vulnerable authenticated functionality.
  • Confirm remediation status against vendor guidance, not assumptions.
Prepared
Confidence
high
Sources
3

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.

cwe · medium confidence lookup

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 lookup
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-13567 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
High
CVSS
8.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.8High
CVSS 3.0 vector shape for CVE-2020-13567Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenEMROpenEMR5.0.2, development version 6.0.0 (commit babec93f600ff1394f91ccd512bcad85832eb6ce)Listed
phpGACLphpGACL3.3.7Listed
Weakness

CWE details

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