vciy

CVE-2024-5217

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Incomplete Input Validation in GlideExpression Script

CVE-2024-52174 of 4 sources documented this
76

rank 76 = 40 + 25 + 0 + 5 + 6

rank@v1 · act now

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.99628 · CISA KEV listed  ·  without this subject the record ranks 36

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 51

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 76

How much of the world it touches

NVD CPE configurations

3 products in the CPE ranges  ·  without this subject the record ranks 71

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 70

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$4.97Mover the next 30 days, if this record is yours
Movement+$4.09Mon 2024-07-31, the last material move, 2 years, 1 month before this reading
Basisassumeda published average, not your estate

$4.97M = $4.99M incident cost x 1 exposure x 0.99628 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.99628EPSSKEV · LISTED
Severity9.2 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationin the wild · KEVreceipt
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2024-07-31, 765 days at 1.00, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
SN9.2 CRITICALreceipt
NVD9.8 CRITICALreceipt
Scoring standard
SNCVSS v4.0receipt
NVDCVSS v3.1receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running ServiceNow Now Platform? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexity · attack requirements presentreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-184 Incomplete List of Disallowed Inputsreceipt
Published consequencesCWE-184: Access Control: Bypass Protection Mechanism[email protected]
Ransomware campaign useUnknown to CISAreceipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 4 Sep 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
CISA remediation statusoverdue since 2024-08-19receipt
CISA required actionApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.receipt
Published to CISA KEV19 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Exploited in the wild · CISA KEV listed, 2024-07-29.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed2024-07-29receipt
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA9.2 CRITICALreceipt
CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.99628 · top 0.05% of all CVEsreceipt
Blast breadth3 products across 1 vendorderived
Assigned bySNreceipt
Recorded changes39 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productServiceNow Now Platformreceipt
Published rangesservicenow utah; servicenow vancouver; servicenow washington_dcreceipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

ServiceNow has addressed an input validation vulnerability that was identified in the Washington DC, Vancouver, and earlier Now Platform releases. This vulnerability could enable an unauthenticated user to remotely execute code within the context of the Now Platform. The vulnerability is addressed in the listed patches and hot fixes below, which were released during the June 2024 patching cycle. If you have not done so already, we recommend applying security patches relevant to your instance as soon as possible. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-184; CWE-697
affected versions
servicenow utah; servicenow vancouver; servicenow washington_dc
also scored by
[email protected] 9.2 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X ·…

The CNA scored it 9.2 and NVD 9.8. Both are shown because both were published; we do not pick one.

check it yourself support.servicenow.com support.servicenow.com darkreading.com receipt

Dated events

2024-07-29Added to CISA KEV2024-07-30EPSS moved 0.01 to 0.142024-07-31EPSS moved 0.14 to 0.962024-08-19CISA remediation due2026-06-15EPSS moved 0.94 to 1.00

Movement the material steps

11 Jul 20240.00043
30 Jul 20240.13967 · crossed 0.10
31 Jul 20240.95999 · crossed 0.50 and 0.90
17 Mar 20250.93689 · scoring model v2025.03.14
15 Jun 20260.99628 · scoring model v2026.06.15
29 Jul 20260.99628

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 28 observations
11 Jul 20240.00043
15 Jul 20240.00054
24 Jul 20240.00896
30 Jul 20240.13967
31 Jul 20240.95999
11 Sep 20240.96091
12 Oct 20240.96160
25 Oct 20240.95996
27 Nov 20240.95842
13 Dec 20240.95575
17 Dec 20240.95194
21 Dec 20240.95024
15 Jan 20250.95217
23 Jan 20250.93386
16 Feb 20250.93057
26 Feb 20250.94833
9 Mar 20250.94585
17 Mar 20250.93689
29 Mar 20250.93937
30 Mar 20250.93689
15 Apr 20250.94196
18 Aug 20250.94155
17 Oct 20250.94108
18 Nov 20250.93654
21 Nov 20250.94108
15 Jun 20260.99628
24 Jul 20260.9953
29 Jul 20260.99628

28 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.99628Published2024-07-10CISA KEV2024-07-29Index as of2026-09-04

Listed by CISA 19 days after it published, exploit probability more than doubled between 2024-07-30 and 2024-07-31 (0.13967 → 0.95999) and the record had been public for 2 years, 1 month when this index was last written.

No material movement in 37 days as of the last ingest this index recorded.

Published 2024-07-10 receipt · CISA KEV 2024-07-29 receipt · Index as of 2026-09-04 derived

Siblings and hubs

Records related to this one

Its defect family

servicenow now platform

Of the 2 records in this family, this is the only one whose title names glideexpression script.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2024-5217.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.