CVE-2026-73529: Improper Restriction of Excessive Authentication Attempts in alextselegidis plainpad
Plainpad through 1.1.1, fixed in commit d3823fc, contains a missing rate limiting vulnerability that allows unauthenticated attackers to send unbounded login requests to the POST /v1/sessions endpoint due to dead code in App\Http\Kernel.php that is never instantiated under the Laravel 11+ skeleton, leaving the API throttle configuration unattached to any route. Attackers can exploit this by sending unlimited credential attempts with no lockout or CAPTCHA enforcement, and additionally trigger CPU exhaustion by forcing repeated bcrypt comparisons on each request.
AI Analysis
Technical Summary
CVE-2026-73529 describes a missing rate limiting vulnerability in Plainpad through version 1.1.1. The vulnerability arises because the API throttle configuration is never attached to any route due to dead code in App\Http\Kernel.php, which is not instantiated under the Laravel 11+ skeleton. As a result, unauthenticated attackers can send unlimited login attempts to the POST /v1/sessions endpoint without any lockout or CAPTCHA enforcement. This allows brute force attacks on credentials and can cause CPU exhaustion by forcing repeated bcrypt password hash comparisons. The issue is resolved in commit d3823fc.
Potential Impact
Attackers can perform unlimited authentication attempts against the Plainpad login API without restriction, enabling brute force attacks to guess credentials. Additionally, the repeated bcrypt computations on each request can lead to CPU exhaustion, potentially degrading service availability. There is no indication of privilege escalation or data exposure beyond the authentication bypass attempts.
Mitigation Recommendations
A fix is available in the commit identified as d3823fc which addresses the missing rate limiting by properly attaching API throttle configuration to the login route. Users should upgrade to a version including this fix. Patch status is not explicitly confirmed beyond the commit reference; check the vendor repository for the fixed version. Until patched, implement external rate limiting or WAF rules to limit login attempts as a temporary mitigation.
CVE-2026-73529: Improper Restriction of Excessive Authentication Attempts in alextselegidis plainpad
Description
Plainpad through 1.1.1, fixed in commit d3823fc, contains a missing rate limiting vulnerability that allows unauthenticated attackers to send unbounded login requests to the POST /v1/sessions endpoint due to dead code in App\Http\Kernel.php that is never instantiated under the Laravel 11+ skeleton, leaving the API throttle configuration unattached to any route. Attackers can exploit this by sending unlimited credential attempts with no lockout or CAPTCHA enforcement, and additionally trigger CPU exhaustion by forcing repeated bcrypt comparisons on each request.
CVSS v4.0
Score 6.9medium
Affected software
alextselegidis
plainpad
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-73529 describes a missing rate limiting vulnerability in Plainpad through version 1.1.1. The vulnerability arises because the API throttle configuration is never attached to any route due to dead code in App\Http\Kernel.php, which is not instantiated under the Laravel 11+ skeleton. As a result, unauthenticated attackers can send unlimited login attempts to the POST /v1/sessions endpoint without any lockout or CAPTCHA enforcement. This allows brute force attacks on credentials and can cause CPU exhaustion by forcing repeated bcrypt password hash comparisons. The issue is resolved in commit d3823fc.
Potential Impact
Attackers can perform unlimited authentication attempts against the Plainpad login API without restriction, enabling brute force attacks to guess credentials. Additionally, the repeated bcrypt computations on each request can lead to CPU exhaustion, potentially degrading service availability. There is no indication of privilege escalation or data exposure beyond the authentication bypass attempts.
Mitigation Recommendations
A fix is available in the commit identified as d3823fc which addresses the missing rate limiting by properly attaching API throttle configuration to the login route. Users should upgrade to a version including this fix. Patch status is not explicitly confirmed beyond the commit reference; check the vendor repository for the fixed version. Until patched, implement external rate limiting or WAF rules to limit login attempts as a temporary mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-12T19:29:19.866Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a84b07ac6e8be0332a47e5a
Added to database: 08/18/2026, 19:20:26 UTC
Last enriched: 08/18/2026, 19:36:23 UTC
Last updated: 10/02/2026, 14:46:10 UTC
Views: 71
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.