vciy

CVE-2024-30262

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.

Contao's remember-me tokens will not be cleared after a password change

CVE-2024-302624 of 4 sources documented this
20

rank 20 = 0 + 18 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00499  ·  without this subject the record ranks 20

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.1, from NVD  ·  without this subject the record ranks 2

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 20

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 18

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 20

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$17,900over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$17,900 = $4.99M incident cost x 0.7179585840212677 exposure x 0.00499 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.00499EPSSNOT IN KEVas of 2026-09-20
Severity5.9 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2024-04-10, 851 days at 0.00, as of 2026-08-09. 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
GitHub_M5.9 MEDIUMreceipt
NVD7.1 HIGHreceipt

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

Running contao? 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 · low privileges required · no user interaction · high attack complexityreceipt
ImpactComplete confidentiality loss; partial integrity lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-613 Insufficient Session Expiration; CWE-384 Session Fixationreceipt
Published consequencesCWE-613: Access Control: Bypass Protection Mechanism[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

First unaffected version, by branchcontao 4.13.40receipt
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.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

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

Authority who says so

CVSS, the CNA5.9 MEDIUMreceipt
CVSS, NVD7.1 HIGHreceipt
Exploit probability0.00499 · top 58% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes20 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productcontaoreceipt
Published rangescontao < 4.13.40receipt

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

Network requestrequires low privilegescontaoCWE-613 weaknessConfidentiality lossC:Hexploits CWE-613data compromise

What it is stated by the CNA

Contao is an open source content management system. Prior to version 4.13.40, when a frontend member changes their password in the personal data or the password lost module, the corresponding remember-me tokens are not removed. If someone compromises an account and is able to get a remember-me token, changing the password would not be enough to reclaim control over the account. Version 4.13.40 contains a fix for the issue. As a workaround, disable "Allow auto login" in the login module. receipt

NVD's analysis a second authority

severity
7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
weakness
CWE-384; CWE-613
affected versions
contao < 4.13.40
also scored by
[email protected] 5.9 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

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

check it yourself github.com github.com receipt

Movement the material steps

10 Apr 20240.00043
17 Mar 20250.00163 · scoring model v2025.03.14
15 Jun 20260.00495 · scoring model v2026.06.15
9 Aug 20260.00499
Show all 20 observations
10 Apr 20240.00043
10 Jan 20250.00049
10 Mar 20250.00052
17 Mar 20250.00163
29 Mar 20250.00234
30 Mar 20250.00163
15 Apr 20250.00033
18 May 20250.00133
22 May 20250.00186
24 May 20250.00208
31 May 20250.00156
29 Aug 20250.00212
17 Oct 20250.00232
24 Oct 20250.00212
18 Nov 20250.00183
21 Nov 20250.00212
1 Mar 20260.00278
28 Apr 20260.00364
15 Jun 20260.00495
9 Aug 20260.00499

20 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.00499Published2024-04-09Index as of2026-08-09

The record had been public for 2 years, 4 months when this index was last written.

Published 2024-04-09 receipt · Index as of 2026-08-09 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.