FortifyFramework / library · Laravel
CVE-2022-25838
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLaravel Fortify before 1.11.1 allows reuse within a short time window, thus calling into question the "OT" part of the "TOTP" concept.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLaravel Fortify before 1.11.1 contains a TOTP reuse vulnerability in its two-factor authentication implementation. The same one-time password can be reused within the valid time window (typically 30 seconds), breaking the fundamental 'one-time' property of TOTP codes and allowing attackers to replay valid authentication tokens.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FortifyFramework / library
< 1.11.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Laravel Fortify is installedCheck your composer.json for 'laravel/fortify' in the require section, or run 'composer show laravel/fortify' to list the packageAffected if The package is not present in the project
-
Check the installed Fortify versionRun 'composer show laravel/fortify' or inspect composer.lock to find the installed version numberAffected if The version is lower than 1.11.1 (e.g., 1.11.0, 1.10.0, etc.)
-
Confirm Two-Factor Authentication is enabled in FortifyInspect config/fortify.php and verify that the 'two-factor-authentication' feature is enabled in the 'features' arrayAffected if Two-factor authentication feature is enabled and Fortify version is below 1.11.1
-
Inspect TOTP validation logic for replay protectionExamine the TwoFactorAuthentication provider in vendor/laravel/fortify/src/Contracts/TwoFactorAuthenticationProvider.php or the related validation class for missing 'usedCodes' tracking or reuse prevention logicAffected if The code does not track or reject previously-used TOTP codes within the valid time window
A system is affected if Laravel Fortify with version below 1.11.1 is installed and Two-Factor Authentication is enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.11.1
Upgrade Laravel Fortify to version 1.11.1 or later. Review authentication logs for any suspicious reuse patterns that may indicate exploitation attempts.
Fortify 1.11.1
- Update Laravel Fortify to version 1.11.1 or later by running: composer require laravel/fortify:^1.11.1
- After updating, run composer install or composer update to install the new version
- Clear the Laravel cache with php artisan config:clear and php artisan cache:clear
- Verify the TOTP reuse vulnerability is fixed by testing that previously used codes are rejected within the time window
- Ensure your application is functioning correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortify
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25838 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25838 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data