Vulnerability Description
OpenProject is an open-source project management application. In versions prior to 17.3.0, 2FA OTP verification in the confirm_otp action of the two_factor_authentication module has no rate limiting, lockout mechanism, or failed-attempt tracking. The existing brute_force_block_after_failed_logins setting only counts password login failures and does not apply to the 2FA verification stage, and neither the fail_login nor stage_failure methods increment any counter, lock the account, or add any delay. With the default TOTP drift window of ±60 seconds allowing approximately 5 valid codes at any time, an attacker who knows a user's password can brute-force the 6-digit TOTP code at roughly 5-10 attempts per second with an expected completion time of approximately 11 hours. The same vulnerability applies to backup code verification. This effectively allows complete 2FA bypass for any account where the password is known. This issue has been fixed in version 17.3.0.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Openproject | Openproject | < 17.3.0 |
Related Weaknesses (CWE)
References
- https://github.com/opf/openproject/security/advisories/GHSA-234r-45m2-w6cvExploitMitigationVendor Advisory
FAQ
What is CVE-2026-33667?
CVE-2026-33667 is a vulnerability with a CVSS score of 7.4 (HIGH). OpenProject is an open-source project management application. In versions prior to 17.3.0, 2FA OTP verification in the confirm_otp action of the two_factor_authentication module has no rate limiting, ...
How severe is CVE-2026-33667?
CVE-2026-33667 has been rated HIGH with a CVSS base score of 7.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-33667?
Check the references section above for vendor advisories and patch information. Affected products include: Openproject Openproject.