vciy

CVE-2013-3900

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.

WinVerifyTrust Signature Validation Vulnerability

CVE-2013-39004 of 4 sources documented this
70

rank 70 = 40 + 19 + 1 + 4 + 6

rank@v1 · act now

Someone is already using it

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

EPSS 0.44647 · CISA KEV listed  ·  without this subject the record ranks 30

What it costs you if it fires

NVD CVSS base score, then the CNA's own

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

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-10-22  ·  without this subject the record ranks 69

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 66

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.36Mover the next 30 days, if this record is yours
Movement-$183,000on 2025-01-07, the last material move, 1 year, 7 months before this reading
Basisassumeda published average, not your estate

$1.36M = $4.99M incident cost x 0.6121449559255632 exposure x 0.44647 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.44647EPSSKEV · LISTED
Severity5.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationin the wild · KEVreceipt
Defenseno fix version held
Movementthreshold crossedreceipt
STEADY10Holding near 0.45 across 64 observations. arc-rules@v1

Foresight · where to check next

Microsoft WindowsFortinetPalo AltoSimpleHelpCVE-2025-478273900

This record is one instance of CWE-347, improper verification of cryptographic signature. The index holds 861 prior instances of this class, 5 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Sources disagree here.

Severity score
Microsoft5.5 MEDIUMreceipt
NVD7.6 HIGHreceipt
Scoring standard
MicrosoftCVSS v3.1receipt
NVDCVSS v2.0receipt

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

Running Microsoft Windows 10 Version 1809? 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.

Reachneeds local access · no privileges required · user interaction required · low attack complexityreceipt
ImpactComplete integrity lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-347 Improper Verification of Cryptographic Signaturereceipt
Published consequencesCWE-347: Access Control, Integrity, Confidentiality: Gain Privileges or Assume Identity, Modify Application Data, Execute Unauthorized Code or Commands[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 2022-07-10receipt
CISA required actionApply updates per vendor instructions.receipt
Published to CISA KEV2952 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Exploited in the wild · CISA KEV listed, 2022-01-10.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 15 public repositories2022-09-06receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2022-01-10receipt
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA5.5 MEDIUMreceipt
CVSS, NVD7.6 HIGHreceipt
Exploit probability0.44647 · top 1% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes78 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows 10 Version 1809; Microsoft Windows Server 2019; Microsoft Windows Server 2019 (Server Core installation); Microsoft Windows Server 2022; Microsoft Windows 11 version 21H2…receipt
Published rangesmicrosoft windows server 2008 r2; microsoft windows server 2012 r2receipt

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.

Attack path

Local accessrequires user interactionCISA KEV listingadded 01-10 · due 07-10Microsoft Windows Server 2019CWE-347 weaknessIntegrity lossI:Hmandates remediationexploits CWE-347data compromise

What it is stated by the CNA

Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update the Security Updates table and to inform customers that the EnableCertPaddingCheck is available in all currently supported versions of Windows 10 and Windows 11. While the format is different from the original CVE published in 2013, except for clarifications about how to configure the EnableCertPaddingCheck registry value, the information herein remains unchanged from the original text published on December 10, 2013, Microsoft does not plan to enforce the stricter verification behavior as a default functionality on supported releases of Microsoft Windows. receipt

Read the rest of the CNA's description

This behavior remains available as an opt-in feature via reg key setting, and is available on supported editions of Windows released since December 10, 2013. This includes all currently supported versions of Windows 10 and Windows 11. The supporting code for this reg key was incorporated at the time of release for Windows 10 and Windows 11, so no security update is required; however, the reg key must be set. See the Security Updates table for the list of affected software. Vulnerability Description A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for portable executable (PE) files. An anonymous attacker could exploit the vulnerability by modifying an existing signed executable file to leverage unverified portions of the file in such a way as to add malicious code to the file without invalidating the signature. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of this vulnerability requires that a user or application run or install a specially crafted, signed PE file. An attacker could modify an... See more at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900

NVD's analysis a second authority

severity
7.6 AV:N/AC:H/Au:N/C:C/I:C/A:C
weakness
CWE-347
affected versions
microsoft windows server 2008 r2; microsoft windows server 2012 r2
also scored by
[email protected] 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N · [email protected] 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H · 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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

check it yourself msrc.microsoft.com receipt

Dated events

2022-01-10Added to CISA KEV2022-05-02EPSS moved 0.44 to 0.502022-07-10CISA remediation due2025-03-17EPSS moved 0.08 to 0.772026-06-15EPSS moved 0.76 to 0.45

Movement the material steps

4 Feb 20220.43621
7 Mar 20230.27071 · scoring model v2023.03.01
6 Sep 20230.41534
22 May 20240.74218 · crossed 0.50
15 Nov 20240.21339 · crossed 0.50
16 Nov 20240.64868 · crossed 0.50
17 Dec 20240.34716 · crossed 0.50
3 Jan 20250.14164
7 Jan 20250.08167 · crossed 0.10
17 Mar 20250.76938 · crossed 0.10 and 0.50 · scoring model v2025.03.14
19 Mar 20250.88115
20 Mar 20250.76938
26 Mar 20250.87197
28 Mar 20250.70928
29 Mar 20250.87197
30 Mar 20250.70928
5 Mar 20260.81249
15 Jun 20260.44647 · crossed 0.50 · scoring model v2026.06.15

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

Show all 64 observations
4 Feb 20220.43621
2 May 20220.49719
7 Mar 20230.27071
8 May 20230.23734
23 Jul 20230.29190
6 Sep 20230.41534
23 Oct 20230.41410
27 Jan 20240.43692
22 May 20240.74218
28 Jun 20240.75612
28 Aug 20240.73512
31 Oct 20240.73940
15 Nov 20240.21339
16 Nov 20240.64868
17 Dec 20240.34716
3 Jan 20250.14164
7 Jan 20250.08167
17 Mar 20250.76938
19 Mar 20250.88115
20 Mar 20250.76938
25 Mar 20250.70928
26 Mar 20250.87197
28 Mar 20250.70928
29 Mar 20250.87197
30 Mar 20250.70928
12 Apr 20250.73007
13 Apr 20250.78559
15 Apr 20250.79965
22 Apr 20250.79689
13 May 20250.76938
15 May 20250.77259
21 May 20250.78854
25 May 20250.79689
26 May 20250.78559
15 Jun 20250.79689
18 Jun 20250.79965
28 Jun 20250.74829
1 Jul 20250.7447
9 Jul 20250.72505
16 Jul 20250.72892
23 Jul 20250.72505
4 Aug 20250.70928
14 Aug 20250.78559
16 Aug 20250.79965
1 Sep 20250.79689
8 Sep 20250.7447
12 Oct 20250.73007
22 Oct 20250.79411
7 Jan 20260.80228
24 Jan 20260.80494
6 Feb 20260.80228
20 Feb 20260.80494
5 Mar 20260.81249
12 Mar 20260.80228
21 Mar 20260.80494
1 Apr 20260.81249
5 Apr 20260.79226
8 Apr 20260.78065
23 Apr 20260.74789
5 May 20260.74441
22 May 20260.76161
8 Jun 20260.75823
14 Jun 20260.7615
15 Jun 20260.44647

64 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.44647Published2013-12-11CISA KEV2022-01-10Public PoC2022-09-06Index as of2026-09-04

Listed by CISA 2952 days after it published, exploit probability more than doubled between 2024-11-15 and 2024-11-16 (0.21339 → 0.64868) and the record had been public for 12 years, 8 months when this index was last written.

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

Published 2013-12-11 receipt · CISA KEV 2022-01-10 receipt · Public PoC 2022-09-06 receipt · Index as of 2026-09-04 derived

The pattern, elsewhere

This record is one instance of CWE-347, improper verification of cryptographic signature. The index holds 861 prior instances of this class, 5 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2020-1464 · Microsoft Windows 10 Version 1803matches 5 of 9KEV listed · 2020receipt
CVE-2025-59718 · Fortinet FortiSwitchManagermatches 4 of 9KEV listed · 2025receipt
CVE-2020-2021 · Palo Alto Networks PAN-OSmatches 3 of 9KEV listed · 2020receipt
CVE-2026-48558 · SimpleHelponly 1 attribute comparableKEV listed · 2026receipt
CVE-2025-47827nothing comparable heldKEV listed · 2025receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

861 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

microsoft windows 10 version 1809

Of the 5 records in this family, this is the only one that does not hold a stated fix version. That is a fact about what the catalogue records, not a finding about exposure.

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-2013-3900.

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.