Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2024-4879: Unauthenticated Jelly Template Injection in ServiceNow Now Platform

Published Jul 10, 2024 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS9.3Critical · v4
EPSS100.0%100th percentile
CISA KEVYesAdded Jul 29, 2024
In the wildActivePer CISA KEV
Vendor
Servicenow
IdentifiersCVE-2024-4879CWE-1287 · Improper Validation of Specified…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

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.

View more in app →
CVE-2024-4879This repository contains a Python exploit script (CVE-2024-4879.py) and a README.md. The script targets ServiceNow instances vulnerable to CVE-2024-4879, a template injection vulnerability. It works by sending a crafted GET request to the /login.do endpoint with a malicious jvar_page_title parameter. If the vulnerability is present, the script attempts to read and dump the contents of the ServiceNow database configuration file (glide.db.properties), extracting sensitive information such as the database name, type, URL, user, and password. The script is operational, providing both detection and exploitation capabilities. It requires a list of target URLs and outputs results to the console, with color-coded status messages. The README provides usage instructions, requirements, and a disclaimer. No hardcoded IPs or domains are present; the script is designed to be used against user-supplied targets.Mr-r00t11 · Disclosed Jul 12, 2024 · python · networkOperationalCVE-2024-4879-ServiceNowThis repository contains a Python exploit (exploit.py) targeting CVE-2024-4879 in ServiceNow's Now Platform (Vancouver, Washington DC Now, and Utah releases). The exploit chains three vulnerabilities (Title Injection, Template Injection Mitigation Bypass, and Filesystem Filter Bypass) to achieve unauthenticated remote code execution via the /login.do endpoint. The script first checks if the target is vulnerable by injecting code that returns a known value. If vulnerable, it proceeds to extract the contents of the 'glide.db.properties' file (containing database credentials) and attempts to dump user credentials from the 'sys_user' table. The exploit is fully operational, requiring only the target's IP address, and provides clear output and file-based results. The repository consists of a README.md (usage instructions and background) and the main exploit script (exploit.py).Praison001 · Disclosed Jul 16, 2024 · python · networkOperationalCVE-2024-4879This repository provides two Nuclei templates for detecting and exploiting CVE-2024-4879, a Jelly Template Injection vulnerability in ServiceNow's Now Platform (Vancouver and Washington DC releases). The main files are 'servicenow.yaml' (for detection via a multiplication result in the response) and 'servicenow-db-exploit.yaml' (for exploitation, extracting database configuration from the server). Both templates use crafted HTTP GET requests to the '/login.do' endpoint, injecting Jelly code via the 'jvar_page_title' parameter. The exploit template attempts to read the 'glide.db.properties' file, which may expose sensitive database credentials if the target is vulnerable. The repository is structured for use with the Nuclei scanning framework and is intended for both detection and exploitation of the vulnerability. No hardcoded IPs or domains are present; the templates are designed to be used against user-specified targets.Brut-Security · Disclosed Jul 12, 2024 · Framework: nuclei · yaml · networkPoC
Exposure surface

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.

VendorProductType
ServicenowServicenowapplication
FAQ

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.
Activity feed

Recent activity

21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+11 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures5YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.