Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-1000489: Mautic versions 2.0.0 - 2.11.0 with a SSO plugin installed could allow a disabled user to still login using em

50
This month
HIGH 8.1REMOTEDOWNGRADEDOWNGRADE

CVE-2017-1000489 is a high-severity flaw (CVSS 8.1) affecting mautic, mautic. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Mautic versions 2.0.0 - 2.11.0 with a SSO plugin installed could allow a disabled user to still login using email address

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance1.1% (top 34%)
CISA exploited listNo
WeaknessCWE-287
Published2018-01-03
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: acquia · mautic

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

acquia mautic DOWNGRADE
Affected: 2.0.0 · 2.0.1 · 2.1.0 · 2.1.1 · 2.2.0 · 2.2.1 · 2.3.0 · 2.4.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy mautic || rpm -q mautic || mautic --version
2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison mautic sudo apt install mautic=<VERSION_BEFORE_2.0.0> sudo apt-mark hold mautic
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mautic sudo dnf downgrade mautic-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add mautic
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
mautic mautic DOWNGRADE
Affected: 2.9.0 · 2.9.2 · 2.10.0 · 2.11.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.9.0
1. Check installed version
apt-cache policy mautic || rpm -q mautic || mautic --version
2. No fixed release: DOWNGRADE to a release before 2.9.0 (Debian / Ubuntu)
apt-cache madison mautic sudo apt install mautic=<VERSION_BEFORE_2.9.0> sudo apt-mark hold mautic
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mautic sudo dnf downgrade mautic-<VERSION_BEFORE_2.9.0> sudo dnf versionlock add mautic
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-1000489?

mautic: downgrade or apply the listed mitigation; mautic: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-1000489 being exploited?

CVE-2017-1000489 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-1000489 affect?

CVE-2017-1000489 affects mautic, mautic. Severity is high (CVSS 8.1). Mautic versions 2.0.0 - 2.11.0 with a SSO plugin installed could allow a disabled user to still login using email address

How urgent is CVE-2017-1000489?

Priority 50/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.