ZDF
Sign inSign up

Vulnerabilities

Security incident · GHSA-xh42-494x-2xgv

Verification code survives verify-email use and remains valid for set-password

Published Oct 5, 2026 · catalog updated Oct 5, 2026 · Verification code survives verify-email

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-xh42-494x-2xgv. A missing EPSS score is not a low risk. Compare Verification code survives verify-email with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Verification code survives verify-email).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
composer craftcms/cms

Craft’s user verification code is a single secret that authorizes two distinct unauthenticated actions — and — but only one of those consumption paths invalidates it. ( , 5.10.13.2) clears only for "pending" users, via ( ). For an already active user who is changing their email address, the function promotes to and returns without clearing the code. The same code is then accepted a second time by , which performs a full password reset. itself correctly nulls the code on use ( ) — only the verify-email path leaks the second use. Net effect: one emailed code yields two independent account-recovery actions instead of one, and the victim’s own legitimate use of the code (verifying the new address) does not consume it. ### Impact An attacker who possesses a victim’s verification code — e.g., observed or leaked from a mailbox, shared inbox, or logs — and who lets (or tricks) the victim into completing the email-change verification can afterward reset the victim’s password with the same code and log in, after the victim reasonably believes the code was consumed. Honest precondition: the attacker must obtain the code out of band, and the flow starts with an email change to an active account. Report ID: 1683

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • composer craftcms/cms>= 5.0.0, < 5.11.0

How to fix GHSA-xh42-494x-2xgv

  • Upgrade

    GHSA-xh42-494x-2xgv lists a fix boundary at 5.11.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 5.11.0

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-xh42-494x-2xgv. A missing EPSS score is not a low risk. Compare Verification code survives verify-email with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 5.0.0, < 5.11.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-287: Improper Authentication. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Craft CMS security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 5, 2026 · Maintainer security tabs

    Detected

    Craft’s user verification code is a single secret that authorizes two distinct unauthenticated actions — and — but only one of those consumption paths invalidates it. ( , 5.10.13.2) clears only for "pending" users, via ( ). For an already active user who is changing their email address, the function promotes to and returns without clearing the code. The same code is then accepted a second time by

Sources

  • Maintainer security tabsVendor advisoryGHSA-xh42-494x-2xgv

    Craft’s user verification code is a single secret that authorizes two distinct unauthenticated actions — and — but only one of those consumption paths invalidates it. ( , 5.10.13.2) clears only for "pending" users, via ( ). For an already active user who is changing their email address, the function promotes to and returns without clearing the code. The same code is then accepted a second time by

    github.com

Freshness

Last verified in this catalog Oct 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026