|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #66653 "Incorrect CAPTCHA" trying to file or comment a bug report
Submitted: 2014-02-06 03:57 UTC Modified: 2019-05-23 13:33 UTC
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: chealer at gmail dot com Assigned:
Status: Open Package: Website problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2014-02-06 03:57 UTC] chealer at gmail dot com
As reported in bug #33449, bug #53255 and bug #66393, CAPTCHAs on have been broken for as long as I can recall.

danielc fixed this in January, as can be seen in bug #66393. According to danielc's latest comment there a few hours ago, the fixes had been deployed. However, I experienced the same issue when reporting bug #66652.

The submission form I'm filling is "48 + 26 = ?" as challenge. My answer is 74, and I am about to click "Send bug report".


I got an error. After clicking, the ITS said "Incorrect Captcha". It now says:

Solve this new problem:
24 - 3 = ?

I entered 21 as answer, and I am about to click "Send bug report" again.


I got a warning:


Are you sure that you searched before you submitted your bug report? We found the following bugs that seem to be similar to yours; please check them before submitting the report as they might contain the solution you are looking for.

If you're sure that your report is a genuine bug that has not been reported before, you can scroll down and click the "Send Bug Report" button again to really enter the details into our database. 

Since I am sure, I am about to do that.


I got another error:
Incorrect Captcha

The form now contains:

Solve the problem:
23 - 19 = ?

I entered 4 as answer and am about to click "Send bug report" once again.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2014-02-06 04:01 UTC] chealer at gmail dot com
The experience I had when filing this report is similar to the one I had when filing bug #66652. I also got several errors when filing #66652. 3 or 4, if I remember correctly. It could be that I entered one incorrect answer once.
 [2018-12-26 18:50 UTC] chealer at gmail dot com
I just filed issue #77348 and had to go through...

    Please enable cookies so the Captcha system can work

...first, before seeing this bug a few times too. No idea if these bugs are technically related.

I just tried posting this very comment, and went through the bug twice already.
 [2018-12-26 19:30 UTC]
Hello, thanks for reporting these. The Captcha system here relies on the session_start() in the code[1] and on having enabled cookies in the browser.

I think I've just found how this issue happens, so stay tuned for a fix in the following days... It happens due to a too simplistic captcha generation. Once the report page is opened one captcha question and answer is generated (for that browser tab). If user opens a new bug page (or report page) in a new browser tab a new answer and question get generated and previous ones are wrong and this strange error pops up. If you possibly spot any more on this issue sooner than me, let me know please.

 [2018-12-26 20:00 UTC]
-Assigned To: +Assigned To: petk
 [2018-12-26 22:50 UTC] chealer at gmail dot com
-Summary: "Incorrect CAPTCHA" trying to file a bug report +Summary: "Incorrect CAPTCHA" trying to file or comment a bug report
 [2018-12-26 22:50 UTC] chealer at gmail dot com
I just got the "Please enable cookies so the Captcha system can work" error again filing #77351.
 [2018-12-26 23:18 UTC] chealer at gmail dot com
Wow. I'm afraid petk is right. I just triggered this bug multiple times filing by reloading in a different tab after each CAPTCHA I was given. I stopped when it became obvious that I could have reproduced this as many times as I wanted.
 [2018-12-27 02:05 UTC] chealer at gmail dot com
I just got the cookies bug again filing #77353. I believe is confused by a session loss.
 [2019-05-23 13:33 UTC]
-Assigned To: petk +Assigned To:
 [2019-05-23 13:33 UTC]
I'm unassigning myself from this issue. According to my evaluations and calculations this project is too messed up to move further. Apologies for trying to slightly improve it. Developer experience here is so low that it is not possible to fix it actually.
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Sat May 25 21:01:27 2019 UTC