CVE-2015-3175: Medium severity moodle vulnerability

Published Jun 1, 2015
·
Updated

Multiple open redirect vulnerabilities in Moodle through 2.5.9, 2.6.x before 2.6.11, 2.7.x before 2.7.8, and 2.8.x before 2.8.6 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via vectors involving an error page that links to a URL from an HTTP Referer header.

Affected Software

39 affected componentsFixes available
composer/moodle/moodle>=2.8.0<2.8.6
2.8.6
composer/moodle/moodle>=2.7.0<2.7.8
2.7.8
composer/moodle/moodle>=2.6.0<2.6.11
2.6.11
composer/moodle/moodle<=2.5.9
Moodle moodle<=2.5.9
Moodle moodle=2.5.0
Moodle moodle=2.5.1
Moodle moodle=2.5.2
Moodle moodle=2.5.3
Moodle moodle=2.5.4
Moodle moodle=2.5.5
Moodle moodle=2.5.6
Moodle moodle=2.5.7
Moodle moodle=2.5.8
Moodle moodle=2.6.0
Moodle moodle=2.6.1
Moodle moodle=2.6.2
Moodle moodle=2.6.3
Moodle moodle=2.6.4
Moodle moodle=2.6.5
Moodle moodle=2.6.6
Moodle moodle=2.6.7
Moodle moodle=2.6.8
Moodle moodle=2.6.9
Moodle moodle=2.6.10
Moodle moodle=2.7.0
Moodle moodle=2.7.1
Moodle moodle=2.7.2
Moodle moodle=2.7.3
Moodle moodle=2.7.4
Moodle moodle=2.7.5
Moodle moodle=2.7.6
Moodle moodle=2.7.7
Moodle moodle=2.8.0
Moodle moodle=2.8.1
Moodle moodle=2.8.2
Moodle moodle=2.8.3
Moodle moodle=2.8.4
Moodle moodle=2.8.5

Event History

Jun 1, 2015
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
May 13, 2022
Advisory Published
via GitHub·01:12 AM

Frequently Asked Questions

1

What is the severity of CVE-2015-3175?

CVE-2015-3175 is considered a medium severity vulnerability due to its potential for exploitation in phishing attacks.

2

How do I fix CVE-2015-3175?

To fix CVE-2015-3175, upgrade Moodle to versions 2.6.11, 2.7.8, or 2.8.6 or later.

3

What kind of attack can be performed using CVE-2015-3175?

CVE-2015-3175 allows attackers to perform open redirect attacks, leading users to arbitrary websites.

4

Which versions of Moodle are affected by CVE-2015-3175?

CVE-2015-3175 affects Moodle versions up to 2.5.9, 2.6.x before 2.6.11, 2.7.x before 2.7.8, and 2.8.x before 2.8.6.

5

Is there a workaround for CVE-2015-3175 while waiting for an update?

There is no specific workaround for CVE-2015-3175; the recommended action is to upgrade to a fixed version.

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