Threats / ServiceNow / CVE-2024-4879
CVE-2024-4879
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
ServiceNow Utah, Vancouver, and Washington DC Now Platform vulnerability
ServiceNow Utah, Vancouver, and Washington DC Now Platform releases contain a Jelly template injection vulnerability in UI macros allowing unauthenticated remote code execution.
Verdict
Today item — known-exploited.
An unauthenticated attacker can inject malicious Jelly templates through UI macros to achieve arbitrary code execution on affected ServiceNow instances. The vulnerability is actively exploited in the wild with high exploit probability.
CISA KEV Yes · 2024-07-295EPSS 0.99976 (verify live)6Exploit Weaponized · public PoC7CVSS 9.33CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-07-29).
Probability (EPSS)
EPSS 0.99976 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.3 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) · Affected: ServiceNow, Utah, Vancouver, and Washington DC Now Platform. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-1287 CWE-1287.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 19 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
WeaknessCWE-1287 · CWE-1287
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify and craft a malicious Jelly template payload targeting the UI macro processing logic.
Business
Attackers gain initial access to the ServiceNow platform without authentication, bypassing security perimeter controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I inject the template through an accessible UI macro endpoint, triggering server-side template processing.
Business
The vulnerability enables remote code execution with the privileges of the ServiceNow application process.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary commands on the underlying infrastructure to establish persistence or exfiltrate data.
Business
Sensitive business data, configurations, and customer information stored in ServiceNow become compromised and subject to theft or manipulation.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.