Skip to content
Fencer Intel
high 8.8

CVE-2022-23940 in the critical feed json

SuiteCRM through 7.12.1 and 8.x through 8.0.1 allows Remote Code Execution.

published 4y ago modified 4mo ago also BIT-suitecrm-2022-23940 , EUVD-2022-28859

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
53.5%
EPSS 53.5% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

SuiteCRM through 7.12.1 and 8.x through 8.0.1 allows Remote Code Execution. Authenticated users with access to the Scheduled Reports module can achieve this by leveraging PHP deserialization in the email_recipients property. By using a crafted request, they can create a malicious report, containing a PHP-deserialization payload in the email_recipients field. Once someone accesses this report, the backend will deserialize the content of the email_recipients field and the payload gets executed. Project dependencies include a number of interesting PHP deserialization gadgets (e.g., Monolog/RCE1 from phpggc) that can be used for Code Execution.

Patch / fix

  • bitnami suitecrm 7.12.5, 8.0.4
  • salesagility suitecrm 7.12.5, 8.0.4

Is CVE-2022-23940 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

53.52% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/manuelz120 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami suitecrm
<7.12.5
>=8.0.0, <8.0.4
7.12.5
8.0.4

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.