Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-5890 Overview
CVE-2024-5890 is an HTML injection vulnerability affecting the ServiceNow Now Platform. An unauthenticated attacker can inject HTML content to modify the appearance of a rendered web page or redirect users to attacker-controlled destinations. The flaw maps to [CWE-79], the class of improper neutralization of input during web page generation.
ServiceNow has released patches for affected instances through standard update channels. The vulnerability requires user interaction, typically clicking a crafted link, to trigger the injected content.
Critical Impact
Unauthenticated attackers can inject HTML into Now Platform pages to deface content or redirect users to malicious sites, enabling phishing and social engineering attacks.
Affected Products
- ServiceNow Now Platform (versions prior to vendor-released patches)
- ServiceNow customer instances that have not applied the KB1710511 remediation
- Hosted and self-managed ServiceNow deployments exposed to untrusted users
Discovery Timeline
- 2024-12-02 - CVE-2024-5890 published to the National Vulnerability Database (NVD)
- 2026-06-17 - Last updated in the NVD database
Technical Details for CVE-2024-5890
Vulnerability Analysis
The vulnerability allows an unauthenticated remote attacker to inject HTML markup into pages rendered by the Now Platform. Because the platform fails to properly neutralize user-supplied input before rendering it in web responses, attacker-controlled markup is treated as part of the page.
Exploitation requires a victim to interact with a crafted URL or request. Once triggered, the injected markup can alter visible page content, insert fake login forms, or redirect the user to an external site. The attack vector is network-based with low complexity and no privileges required.
The underlying weakness is [CWE-79], Improper Neutralization of Input During Web Page Generation. Unlike full cross-site scripting, this issue is scoped to HTML injection, which still enables defacement, phishing lures, and clickjacking preludes against authenticated session holders.
Root Cause
The Now Platform did not consistently sanitize or encode user-controlled input rendered into HTML responses. Characters that carry structural meaning in HTML, such as <, >, and attribute delimiters, were passed through to the browser instead of being escaped. This allowed arbitrary markup to influence the Document Object Model (DOM) presented to the user.
Attack Vector
An attacker crafts a URL or request containing HTML payloads targeting a vulnerable Now Platform endpoint. The victim is lured into clicking the link through phishing or embedded references. When the response renders, the injected markup appears in the context of the trusted ServiceNow origin, which legitimizes phishing overlays or redirect prompts.
No authentication is required to craft or deliver the payload. The attacker does not need a ServiceNow account on the target instance.
Technical specifics of the injection point and payload format are documented in the vendor advisory. See the ServiceNow Knowledge Base Article KB1710511 for implementation details.
Detection Methods for CVE-2024-5890
Indicators of Compromise
- Inbound HTTP requests to Now Platform endpoints containing encoded or raw HTML tags such as <iframe>, <a href=>, <meta http-equiv="refresh">, or <img> within query parameters
- Web server logs showing unusually long query strings or URL-encoded angle brackets (%3C, %3E) directed at ServiceNow URIs
- User reports of unexpected redirects, foreign branding, or spoofed login prompts on ServiceNow pages
Detection Strategies
- Deploy web application firewall (WAF) rules that inspect query parameters and POST bodies destined for ServiceNow for HTML tag patterns
- Correlate referrer headers and outbound redirect chains originating from ServiceNow domains to flag anomalous destinations
- Review ServiceNow transaction logs for requests from unauthenticated sessions that include characters typical of markup injection
Monitoring Recommendations
- Enable verbose HTTP access logging on the perimeter in front of ServiceNow instances and retain logs for retrospective analysis
- Alert on repeated 200-OK responses to unauthenticated requests containing suspicious URL parameters
- Monitor user-reported phishing tied to ServiceNow URLs and route reports to incident response for payload extraction
How to Mitigate CVE-2024-5890
Immediate Actions Required
- Apply the security update referenced in ServiceNow KB1710511 to all affected Now Platform instances
- Inventory every ServiceNow instance, including non-production and sandbox environments, and confirm patch status
- Restrict unauthenticated access to Now Platform endpoints where business requirements allow
Patch Information
ServiceNow released fixes through its standard patching channels. Customers should consult the vendor knowledge base article for the specific hotfix, patch bundle, or Now Platform release that remediates CVE-2024-5890 on their version family. Hosted customers typically receive updates through ServiceNow-managed maintenance windows; self-managed deployments must schedule the update manually.
Workarounds
- Place a WAF or reverse proxy in front of ServiceNow and block requests containing raw or URL-encoded HTML tags in parameters
- Enforce a strict Content Security Policy (CSP) on the ServiceNow origin to limit the impact of injected markup where supported
- Train users to validate ServiceNow URLs before clicking and to report unexpected redirects or page content changes
# Example WAF rule concept to block HTML tag characters in ServiceNow query strings
# (ModSecurity-style pseudo-rule - adapt to your WAF syntax)
SecRule REQUEST_URI "@contains /now/" \
"chain,phase:2,deny,status:403,id:1005890,msg:'CVE-2024-5890 HTML injection attempt'"
SecRule ARGS "@rx (?i)(%3C|<)(script|iframe|img|meta|a |svg)" \
"t:none,t:urlDecodeUni"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

