LiveActive security incident?Get immediate response
CVE Record

CVE-2023-2852: SQLi in SoftMed's SelfPatron

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Softmed SelfPatron allows SQL Injection.This issue affects SelfPatron : before 2.0.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Softmed SelfPatron versions before 2.0 are reported vulnerable to SQL injection. An unauthenticated remote attacker could potentially read, change, or disrupt application data if an exposed vulnerable instance is reachable. The public source bundle does not show confirmed exploitation.

Executive priority

Treat this as urgent where SelfPatron is deployed. The technical severity is critical because compromise could affect patient-facing application data, but urgency depends on whether the organization actually runs vulnerable versions and whether they are reachable.

Technical view

CVE-2023-2852 is CWE-89 SQL injection in Softmed SelfPatron before 2.0. CVSS 3.1 is 9.8: network attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to organizations running Softmed SelfPatron before 2.0, especially internet-facing deployments. The provided affected-version metadata is sparse, so teams should verify product/version records directly rather than assuming non-exposure.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. The CVSS vector indicates exploitation would not require authentication or user interaction if a vulnerable instance is reachable.

Researcher notes

The public bundle provides vulnerability class, affected range, CVSS, and a USOM reference, but little operational detail. Avoid assuming exploit availability, affected configurations beyond SelfPatron before 2.0, or a specific patch mechanism unless confirmed by vendor guidance.

Mitigation direction

  • Identify all Softmed SelfPatron deployments and owners.
  • Move SelfPatron instances off versions before 2.0 per vendor guidance.
  • Restrict external access until version status is verified.
  • Check Softmed or USOM advisories for authoritative remediation details.
  • Preserve logs before making emergency changes.

Validation and detection

  • Confirm the deployed SelfPatron version on every instance.
  • Verify whether any SelfPatron instance is internet-facing.
  • Review application and database logs for unusual SQL errors or data access.
  • Confirm remediation against vendor or USOM guidance.
  • Document any compensating controls and remaining exposed instances.
Prepared
Confidence
medium
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-2023-2852 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-2852Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
SoftmedSelfPatron0unaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.