LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32102: A SQL injection vulnerability exists (with user privileges) in library/custom_template/ajax_code.php in Ope...

A SQL injection vulnerability exists (with user privileges) in library/custom_template/ajax_code.php in OpenEMR 5.0.2.1.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenEMR 5.0.2.1 has a reported SQL injection flaw that requires normal user privileges. In a healthcare records system, that can threaten sensitive patient data if an attacker has or obtains an account. The source bundle does not provide a CVSS score or confirmed active exploitation.

Executive priority

Prioritize remediation if OpenEMR 5.0.2.1 is in use, because authenticated SQL injection in an EHR platform can put patient records and operational trust at risk. Urgency is lower where the product is absent or already upgraded.

Technical view

CVE-2021-32102 is described as SQL injection in library/custom_template/ajax_code.php in OpenEMR 5.0.2.1, with user privileges required. The bundle lists no CVSS, CWE, CPE, or detailed affected-version range. Related sources discuss OpenEMR 5.0.2.1 flaws and OpenEMR 5.0.2 Patch 5, but exact fix mapping is not fully evidenced here.

Likely exposure

Likely limited to organizations running OpenEMR 5.0.2.1, especially where authenticated users can access custom template functionality. Exposure is higher for internet-facing patient or staff portals, but the CVE description indicates user privileges are required.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. Public vulnerability writeups exist for OpenEMR 5.0.2.1, so defenders should assume technical details may be known, while avoiding claims of exploitation in the wild.

Researcher notes

Evidence is thin: the CVE record names the file and version, but lacks CVSS, CWE, and CPE data. References discuss serious OpenEMR 5.0.2.1 issues and Patch 5, but this bundle does not conclusively map every fix detail to CVE-2021-32102.

Mitigation direction

  • Identify any OpenEMR 5.0.2.1 deployments.
  • Review OpenEMR 5.0.2 Patch 5 and current vendor guidance.
  • Upgrade to a vendor-supported OpenEMR release where feasible.
  • Restrict access to OpenEMR administrative and authenticated user surfaces.
  • Review suspicious authenticated activity involving custom template features.

Validation and detection

  • Confirm exact OpenEMR version and patch level.
  • Check whether library/custom_template/ajax_code.php exists in deployed code.
  • Inventory accounts with access to custom template functionality.
  • Review application and database logs for unusual authenticated queries.
  • Verify vendor guidance identifies the applicable fixed release.
Prepared
Confidence
medium
Sources
6

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-2021-32102 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
6Source links

CVSS and timeline data

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

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.