CVE-2024-4879: Unauthenticated Jelly Template Injection in ServiceNow Now Platform
- Vendor
- Servicenow
CVE-2024-4879 is an input-validation vulnerability in ServiceNow Now Platform UI macros affecting unpatched Vancouver and Washington DC releases, with affected Utah releases also covered by security fixes. An unauthenticated attacker can inject content through the jvar_page_title query parameter into a page-title template rendered without escaping. The HTML sanitizer permits style elements, allowing attacker-controlled XML/Jelly template content to survive sanitization and enter the platform's two-phase template-rendering process. Exploitation can enable remote code execution within the Now Platform context. The vulnerability has been actively exploited, including in chains with CVE-2024-5178 and CVE-2024-5217.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise the confidentiality, integrity, and availability of a ServiceNow instance through unauthorized server-side code execution, sensitive-data access, data modification, and operational disruption. Exploitation chains involving CVE-2024-5178 and CVE-2024-5217 can extend access to instance databases, database credentials, user password hashes, and protected local files. Where MID Servers are configured, platform compromise can enable command execution on those servers and provide a route into connected internal networks. Data-theft attacks against private organizations and government agencies have involved these vulnerabilities.
Mitigation
If you can’t patch tonight, do this now.
Until patches are applied, reduce exposure by restricting network and application access to affected instances and UI components wherever operationally feasible. Increase monitoring of application and access logs for unexpected page-title parameters, Jelly template syntax, code-evaluation probes, unusual data queries, and suspicious MID Server activity. Investigate anomalies promptly. These measures reduce exposure and improve detection but do not replace the vendor fixes.
Remediation
Patch, then assume compromise.
Apply the ServiceNow security patch or hotfix appropriate to the instance's release branch, or upgrade to a later release containing the fix. Fixed Utah versions include Patch 10 Hot Fix 3 and Patch 10a Hot Fix 2. Fixed Vancouver versions include Patch 6 Hot Fix 2, Patch 7 Hot Fix 3b, Patch 8 Hot Fix 4, Patch 9, and Patch 10. Fixed Washington DC versions include Patch 1 Hot Fix 2b, Patch 2 Hot Fix 2, Patch 3 Hot Fix 1, and Patch 4. ServiceNow applied updates to hosted instances and supplied updates to partners and self-hosted customers; verify the actual patch status of each instance. Also apply the separate fixes for CVE-2024-5178 and CVE-2024-5217 because their required patch levels can differ. Investigate potential historical compromise, since patching does not remove access or remediate data exposure resulting from prior exploitation.
Exploits
3 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2024-4879 exploited in the wild?
- Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jul 29, 2024.
- Is there a public exploit for CVE-2024-4879?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2024-4879, the earliest disclosed Jul 12, 2024.
- Is there a patch for CVE-2024-4879?
- Apply the ServiceNow security patch or hotfix appropriate to the instance's release branch, or upgrade to a later release containing the fix. Fixed Utah versions include Patch 10 Hot Fix 3 and Patch 10a Hot Fix 2.
- What products are affected by CVE-2024-4879?
- Servicenow.
- How severe is CVE-2024-4879?
- CVE-2024-4879 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 100.0% (100th percentile) as of Nov 4, 2026.
Recent activity
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.