CVE-2017-7620: CSRF

Published May 21, 2017
·
Updated

MantisBT before 1.3.11, 2.x before 2.3.3, and 2.4.x before 2.4.1 omits a backslash check in stringapi.php and consequently has conflicting interpretations of an initial \/ substring as introducing either a local pathname or a remote hostname, which leads to (1) arbitrary Permalink Injection via CSRF attacks on a permalinkpage.php?url= URI and (2) an open redirect via a loginpage.php?return= URI.

Affected Software

14 affected componentsFixes available
MantisBT mantisbt<=1.3.10
MantisBT mantisbt=2.0.0
MantisBT mantisbt=2.0.1
MantisBT mantisbt=2.1.0
MantisBT mantisbt=2.1.1
MantisBT mantisbt=2.1.2
MantisBT mantisbt=2.2.0
MantisBT mantisbt=2.2.2
MantisBT mantisbt=2.2.3
MantisBT mantisbt=2.2.4
MantisBT mantisbt=2.4.0
composer/mantisbt/mantisbt>=2.4.0<2.4.1
2.4.1
composer/mantisbt/mantisbt>=2.0.0<2.3.3
2.3.3
composer/mantisbt/mantisbt<1.3.11
1.3.11

Event History

May 21, 2017
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·02:34 AM

Frequently Asked Questions

1

What is the severity of CVE-2017-7620?

CVE-2017-7620 is considered a medium severity vulnerability.

2

How do I fix CVE-2017-7620?

To fix CVE-2017-7620, upgrade MantisBT to version 1.3.11 or 2.3.3 and later.

3

What versions of MantisBT are affected by CVE-2017-7620?

CVE-2017-7620 affects MantisBT versions before 1.3.11 and 2.x versions before 2.3.3 and 2.4.x before 2.4.1.

4

What type of attack does CVE-2017-7620 allow?

CVE-2017-7620 allows for arbitrary permalink injection via a cross-site request forgery (CSRF) attack.

5

Is there a workaround for CVE-2017-7620 if I cannot upgrade MantisBT?

There are no recommended workarounds for CVE-2017-7620; upgrading is the only effective solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203