Incompatibility with MantisBT (web-based bug tracker)?

Description of the issue:

Brave seems to exhibit issues with MantisBT bug tracker web sites, though since I only have an account on one, it is hard to know for sure if this is widespread.

When performing certain tasks like setting up a new tracker, or editing an existing tracker, one gets:


Invalid form security token. This could be caused by a session timeout, or accidentally submitting the form twice.

Please use the “Back” button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.

Using the Back button does not remediate the issue. Whether a double-submission occurred or not, such is not at the request of the human operating the browser, and as far as a “timeout” goes, the problem occurs when the user is prompt at filling out the forms.

Exact URL of the website in question:

The exact URL where this was observed is not public, but the MantisBT project uses its own software for its Bug Tracker here:

To trigger an error, one would have to have a legitimate account and be able to create a new bug or edit an existing one.

On the site where this was observed, MantisBT details were:

|MantisBT Version|2.23.0|
|Schema Version|210|
|PHP Version|7.3.27|
|Database Driver|mysqli|
|Database Version, Description|5.5.68, 5.5.68-MariaDB|

Neither Firefox nor Chrome exhibit this behavior.

Did the issue present with default Shields settings? (yes/no)


Does the site function as expected when Shields are turned off?


Is there a specific Shields configuration that causes the site to break? If so, tell us that configuration. (yes/no):


Does the site work as expected when using Chrome?

Yes Version 88.0.4324.190 (Official Build) (64-bit)
Yes Version 89.0.4389.82 (Official Build) (64-bit)

Brave version (check About Brave):

Version 1.21.74 Chromium: 89.0.4389.72 (Official Build) (64-bit)

Hey @Brayvin

I’ve created an account. What steps in creating a new report should I need to do?

I have triggered the issue 2 different ways.

Editing an existing issue:

  1. Use the View Issues tab to find and select an issue to edit.
  2. Either open the issue by:
    a) clicking the ID to open it, then clicking the Edit button, or
    b) Click the pencil icon by the issue to edit.
  3. Make a change to the text in one of the text fields.
  4. Click the Update Information button.
  5. Observe the “APPICATION ERROR #2800”.

Creating a new issue

When the bug occurs, no actual new posting will occur.

  1. Go to the Report Issue tab
  2. As needed, use a “Select Project” dropdown and then click “Select Project”
  3. Select a Category and edit required fields: Summary, Description
  4. Click “Submit Issue” at the bottom of the form.
  5. Observe the “APPICATION ERROR #2800”.

Another way:

  1. Use the View Issues tab to find and select an issue to edit.
  2. Oen the issue by: a) clicking the ID to open it
  3. Go to the Add Note form a the bottom.
  4. Enter some Note text.
  5. Click “Add Note”.
  6. Observe the “APPICATION ERROR #2800”.

See also:

I went ahead and also created an account on the official Bug Tracker. The problem was not evident. The MantisBT version there is newer than the one where the problem was observed. They are running:

MantisBT 2.26.0-dev-master-c9c3915

I’ll see about trying to reproduce this on a latest production version of MantisBT. No pencil seen, issue was created without issue.

Also comments worked fine (in other tickets). Maybe its a serverside permissions, but creating a ticket, no option for an edit.

Please consider this resolved by an upgrade of the MantisBT installation from 2.23 to 2.25.

1 Like

Thanks for the followup, good to see it working

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.