CVE-2024-7954

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2024-08-23. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2024-48791 (ENISA EUVD) · GHSA-42mv-3h37-wfh9 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 90%
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 90%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

The porte_plume plugin used by SPIP before 4.30-alpha2, 4.2.13, and 4.1.16 is vulnerable to an arbitrary code execution vulnerability. A remote and unauthenticated attacker can execute arbitrary PHP as the SPIP user by sending a crafted HTTP request.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
95
EG Risk 95/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation90% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
90%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
90% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 23, 2024

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Oct 8, 2026
Patch available.
Web page

SPIP porte_plume plugin Arbitrary PHP Execution | Advisories | VulnCheck

https://vulncheck.com/advisories/spip-porte-plume
Web page

Spip Preauth RCE 2024: Part 1, The Feather • Think Love Share

https://thinkloveshare.com/hacking/spip_preauth_rce_2024_part_1_the_feather/
Web page

Mise à jour critique de sécurité : sortie de SPIP 4.3.0-alpha2, SPIP 4.2.13, (…) - SPIP Blog

https://blog.spip.net/Mise-a-jour-critique-de-securite-sortie-de-SPIP-4-3-0-alpha2-SPIP-4-2-13-SPIP-4.html

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
spip—
  • every version up to 4.3.0+dfsg-1: fixed in 4.3.0+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
spip—
  • every version up to 4.3.0+dfsg-1: fixed in 4.3.0+dfsg-1
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 162 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 62 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 01:20 UTCEchelonGraph re-scored
  2. 2026-11-13 01:20 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-12 00:24 UTCEchelonGraph re-scored
  4. 2026-11-12 00:24 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-11 16:35 UTCEPSS rescoreEPSS 90% · 99th percentile
  6. 2026-11-10 23:28 UTCEchelonGraph re-scored
  7. 2026-11-10 23:28 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-09 22:31 UTCEchelonGraph re-scored
  9. 2026-11-09 22:31 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-09 16:32 UTCEPSS rescoreEPSS 90% · 99th percentile
  11. 2026-11-08 21:35 UTCEchelonGraph re-scored
  12. 2026-11-08 21:35 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-08 16:36 UTCEPSS rescoreEPSS 90% · 99th percentile
  14. 2026-11-07 20:39 UTCEchelonGraph re-scored
  15. 2026-11-07 20:39 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-06 19:43 UTCEchelonGraph re-scored
  17. 2026-11-06 19:43 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-06 16:33 UTCEPSS rescoreEPSS 90% · 99th percentile
  19. 2026-11-05 18:47 UTCEchelonGraph re-scored
  20. 2026-11-05 18:47 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-05 06:25 UTCOSV refresh
  22. 2026-11-04 17:51 UTCEchelonGraph re-scored
  23. 2026-11-04 17:51 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-04 16:32 UTCEPSS rescoreEPSS 90% · 99th percentile
  25. 2026-11-03 16:55 UTCEchelonGraph re-scored
Show 74 more
  1. 2026-11-03 16:55 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-11-02 16:41 UTCEPSS rescoreEPSS 90% · 99th percentile
  3. 2026-11-02 15:59 UTCEchelonGraph re-scored
  4. 2026-11-02 15:59 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-01 15:03 UTCEchelonGraph re-scored
  6. 2026-11-01 15:03 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-31 14:07 UTCEchelonGraph re-scored
  8. 2026-10-31 14:07 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-30 13:09 UTCEchelonGraph re-scored
  10. 2026-10-30 13:09 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-29 16:31 UTCEPSS rescoreEPSS 90% · 99th percentile
  12. 2026-10-29 12:13 UTCEchelonGraph re-scored
  13. 2026-10-29 12:12 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-28 11:09 UTCEchelonGraph re-scored
  15. 2026-10-28 11:09 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-27 09:30 UTCEchelonGraph re-scored
  17. 2026-10-27 09:30 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-26 08:34 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-25 16:52 UTCEchelonGraph re-scored
  20. 2026-10-25 16:30 UTCEPSS rescoreEPSS 90% · 99th percentile
  21. 2026-10-25 07:39 UTCEchelonGraph re-scored
  22. 2026-10-25 07:39 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-24 06:43 UTCEchelonGraph re-scored
  24. 2026-10-24 06:42 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-23 05:45 UTCEchelonGraph re-scored
  26. 2026-10-23 05:45 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-22 16:32 UTCEPSS rescoreEPSS 90% · 99th percentile
  28. 2026-10-22 04:48 UTCEchelonGraph re-scored
  29. 2026-10-22 04:48 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-21 16:30 UTCEPSS rescoreEPSS 90% · 99th percentile
  31. 2026-10-21 03:51 UTCEchelonGraph re-scored
  32. 2026-10-21 03:51 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-20 02:55 UTCEchelonGraph re-scored
  34. 2026-10-20 02:55 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-19 01:59 UTCEchelonGraph re-scored
  36. 2026-10-19 01:58 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-18 05:55 UTCEchelonGraph re-scored
  38. 2026-10-18 01:01 UTCEchelonGraph re-scored
  39. 2026-10-18 01:01 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-17 00:03 UTCEchelonGraph re-scored
  41. 2026-10-17 00:03 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-15 20:58 UTCEchelonGraph re-scored
  43. 2026-10-15 20:57 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-14 16:30 UTCEPSS rescoreEPSS 90% · 99th percentile
  45. 2026-10-14 15:06 UTCEchelonGraph re-scored
  46. 2026-10-14 15:06 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-13 14:09 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-12 17:33 UTCEchelonGraph re-scored
  49. 2026-10-12 12:50 UTCEchelonGraph re-scored
  50. 2026-10-12 12:49 UTCGHSA enrichmentGHSA-42mv-3h37-wfh9 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-11 21:00 UTCEchelonGraph re-scored
  52. 2026-10-11 15:52 UTCEchelonGraph re-scored
  53. 2026-10-09 20:06 UTCEPSS rescoreEPSS 90% · 99th percentile
  54. 2026-10-07 23:46 UTCEPSS rescoreEPSS 90% · 99th percentile
  55. 2026-10-07 09:05 UTCOSV refresh
  56. 2026-10-02 17:55 UTCEchelonGraph re-scored
  57. 2026-10-01 19:48 UTCEPSS rescoreEPSS 90% · 99th percentile
  58. 2026-09-24 14:02 UTCEPSS rescoreEPSS 90% · 99th percentile
  59. 2026-09-22 14:47 UTCEPSS rescoreEPSS 90% · 99th percentile
  60. 2026-09-17 14:50 UTCOSV refresh
  61. 2026-09-13 16:45 UTCEPSS rescoreEPSS 90% · 99th percentile
  62. 2026-09-11 09:35 UTCEPSS rescoreEPSS 90% · 99th percentile
  63. 2026-09-10 09:33 UTCEPSS rescoreEPSS 90% · 99th percentile
  64. 2026-09-07 16:00 UTCEPSS rescoreEPSS 90% · 99th percentile
  65. 2026-09-06 13:46 UTCEPSS rescoreEPSS 90% · 99th percentile
  66. 2026-08-30 19:16 UTCEPSS rescoreEPSS 90% · 99th percentile
  67. 2026-08-29 15:13 UTCOSV refresh
  68. 2026-08-28 21:39 UTCEPSS rescoreEPSS 90% · 99th percentile
  69. 2026-08-27 14:24 UTCEPSS rescoreEPSS 90% · 99th percentile
  70. 2026-08-24 14:15 UTCEPSS rescoreEPSS 90% · 99th percentile
  71. 2026-08-21 23:47 UTCEPSS rescoreEPSS 90% · 99th percentile
  72. 2026-08-19 17:02 UTCEPSS rescoreEPSS 90% · 99th percentile
  73. 2026-08-18 13:47 UTCEPSS rescoreEPSS 90% · 99th percentile
  74. 2026-08-16 02:13 UTCEPSS rescoreEPSS 90% · 99th percentile

Publicly available exploits

(7 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 5 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitexploit/multi/http/spip_porte_plume_previsu_rce✓ verified
    Published Aug 21, 2024

    SPIP Unauthenticated RCE via porte_plume Plugin

    Open source ↗
  • GitHub PoC0dayan0n/RCE_CVE-2024-7954-
    Published Dec 28, 2024

    The porte_plume plugin used by SPIP before 4.30-alpha2, 4.2.13, and 4.1.16 is vulnerable to an arbitrary code execution vulnerability. A remote and unauthenticated attacker can execute arbitrary PHP as the SPIP user by sending a crafted HTTP request. (CRITICAL)

    Open source ↗
  • GitHub PoCTheCyberguy-17/RCE_CVE-2024-7954
    Published Sep 23, 2024
    Open source ↗
  • GitHub PoCgh-ost00/CVE-2024-7954-RCE
    Published Sep 1, 2024

    Unauthenticated Remote Code Execution in SPIP versions up to and including 4.2.12

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-7954.yaml
    Published Aug 29, 2024

    SPIP Porte Plume Plugin - Remote Code Execution

    Open source ↗
  • GitHub PoCbigb0x/CVE-2024-7954
    Published Aug 28, 2024

    This exploit will attempt to execute system commands on SPIP targets.

    Open source ↗
  • GitHub PoCChocapikk/CVE-2024-7954
    Published Aug 10, 2024

    Unauthenticated Remote Code Execution in SPIP versions up to and including 4.2.12

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-7954?
CVE-2024-7954 is a critical-severity vulnerability; its CVE record was published on August 23, 2024. The porte_plume plugin used by SPIP before 4.30-alpha2, 4.2.13, and 4.1.16 is vulnerable to an arbitrary code execution vulnerability. A remote and unauthenticated attacker can execute arbitrary PHP as the SPIP user by sending a crafted HTTP request.
When was the CVE record for CVE-2024-7954 published?
The CVE record for CVE-2024-7954 was published on August 23, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-7954 actively exploited?
CVE-2024-7954 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-7954?
CVE-2024-7954 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-7954?
A fix for CVE-2024-7954 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-7954

Explore →

Is Your Infrastructure Affected by CVE-2024-7954?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs