Vulnerability report

Trusted Third Party Report Confirmed Confidence In CISA KEV

CVE-2023-22952

SugarCRM

SugarCRM

Severity
CVSS 8.8 · High
Confidence
Confirmed
Exploit status
Trusted Third Party Report
EPSS
80.1%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2023-22952 is a vulnerability affecting SugarCRM. In SugarCRM before 12.0. Hotfix 91155, a crafted request can inject custom PHP code through the EmailTemplates because of missing input validation.

Have exploitation attempts been observed?

Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Listed in CISA KEV. Confidence is confirmed.

Who is affected?

SugarCRM.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

In SugarCRM before 12.0

In SugarCRM before 12.0. Hotfix 91155, a crafted request can inject custom PHP code through the EmailTemplates because of missing input validation.

Published
11 Jan 2023
Exploitation Attempts Reported
02 Feb 2023
Attack vector
Remote
Complexity
Low
Privileges
Low
User interaction
None

Tags

nuclei_scanner php cisa metasploit metasploit_scanner

CVE References

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation Attempts Observed in the Wild

CISA

Recorded 02 Feb 2023

A trusted third party reported exploitation attempts.

Proof of concept available

Nuclei Templates

Recorded 28 Apr 2025

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CISA First 2023-02-02 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

8.8 High

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

80.1%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

sugarcrm_webshell_cve_2023_22952

metasploit · Created Unknown

Metasploit module for CVE-2023-22952

Timeline

From disclosure to observed exploitation attempts

  1. 15:02 UTC

    Metasploit module available

    Exploit module available

  2. 15:02 UTC

    Public PoC available

    Public proof-of-concept code published

  3. 00:00 UTC

    Nuclei template available

    Scanner coverage available

  4. 00:00 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  5. 00:00 UTC

    CVE published

    Vulnerability disclosed publicly

  6. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2023-22952

Sample API response
{
  "cve_id": "CVE-2023-22952",
  "confidence": "Confirmed",
  "cvss_score": 8.8,
  "cvss_estimated": false,
  "epss_score": 0.80139,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}