CAPTCHA
The module remembers when a test has been passed but does not properly clear that memory. Someone could submit a protected form multiple times without passing a new test. They could not read or change any existing data.
- Who could do thisAnyone visiting the site. No login needed.
- Does it apply to youAny site using this module.
- Has it been used in attacksYes. It has been used in real attacks.
- How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.
Tell your developerUpdate CAPTCHA to 2.0.11 or 8.x-1.18, whichever branch you are on.
For developers: what the fix changed
The fix updates _captcha_update_captcha_session in captcha.inc to set the session status to unsolved and modifies _captcha_get_posted_captcha_info in captcha.module to only query unsolved sessions, preventing session reuse.
Also in this release The release also integrates with CrowdSec, removes deprecated imagedestroy calls for PHP 8.5 compatibility, and updates Tugboat preview settings.
.gitlab-ci.yml+0 −1.tugboat/config.yml+1 −1captcha.inc+1 −0 fixcaptcha.module+33 −15 fixcomposer.json+3 −0modules/image_captcha/image_captcha.admin.inc+0 −1modules/image_captcha/src/Controller/CaptchaFontPreviewController.php+1 −2modules/image_captcha/src/Controller/CaptchaImageGeneratorController.php+1 −2src/Plugin/CrowdsecScenario/FailedCaptchaScenario.php+20 −0