Skip to content
Fencer Intel
critical 10.0

CVE-2023-22621 in the critical feed json

Strapi plugins vulnerable to Server-Side Template Injection and Remote Code Execution in the Users-Permissions Plugin

published 3y ago modified 4mo ago also GHSA-2h87-4q2w-v4hf , EUVD-2023-1157

cvss
10.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
70.6%
EPSS 70.6% chance of exploitation in 30 days, percentile 99.4%
public exploits
0
none known

Summary

Strapi through 4.5.5 allows authenticated Server-Side Template Injection (SSTI) that can be exploited to execute arbitrary code on the server. A remote attacker with access to the Strapi admin panel can inject a crafted payload that executes code on the server into an email template that bypasses the validation checks that should prevent code execution.

Patch / fix

  • npm @strapi/plugin-users-permissions 4.5.6
  • npm @strapi/plugin-email 4.5.6
  • strapi strapi 4.5.6

Is CVE-2023-22621 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

70.60% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • ghostccamm.com https://www.ghostccamm.com/blog/multi_strapi_vulns/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm @strapi/plugin-users-permissions
<4.5.6
4.5.6
npm @strapi/plugin-email
<4.5.6
4.5.6

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

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.