CVE-2018-1000089: Anymail django-anymail version version 0.2 through 1.3 contains a CWE-532, CWE-209 vulnerability in WEBHOOK_AU

This month

HIGH 7.4REMOTEUPGRADE

CVE-2018-1000089 is a high-severity flaw (CVSS 7.4) affecting django-anymail. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Anymail django-anymail version version 0.2 through 1.3 contains a CWE-532, CWE-209 vulnerability in WEBHOOK_AUTHORIZATION setting value that can result in An attacker with access to error logs could fabricate email tracking events. This attack appear to be exploitable via If you have exposed your Django error reports, an attacker could discover your ANYMAIL_WEBHOOK setting and use this to post fabricated or malicious Anymail tracking/inbound even

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.4 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Weakness	CWE-532
Published	2018-03-13
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: django-anymail project

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

Am I affected?

Timeline

2018-03-13 15:29 UTCPublished CVE record published
2026-06-17 01:32 UTCUpdated Record last modified

django-anymail project django-anymail UPGRADE

Affected: >= 0.2 and <= 1.3

Fixed in: newer than 1.3

Safe to downgrade to: a release before 0.2

1. Check installed version

apt-cache policy django-anymail || rpm -q django-anymail || django-anymail --version

2. UPGRADE to newer than 1.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django-anymail

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django-anymail

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.2 (Debian / Ubuntu)

apt-cache madison django-anymail sudo apt install django-anymail=<VERSION_BEFORE_0.2> sudo apt-mark hold django-anymail

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list django-anymail sudo dnf downgrade django-anymail-<VERSION_BEFORE_0.2> sudo dnf versionlock add django-anymail

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-2018-1000089?

django-anymail: upgrade to newer than 1.3. Exact commands for each OS are on this page.

Is CVE-2018-1000089 being exploited?

CVE-2018-1000089 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-2018-1000089 affect?

CVE-2018-1000089 affects django-anymail. Severity is high (CVSS 7.4). Anymail django-anymail version version 0.2 through 1.3 contains a CWE-532, CWE-209 vulnerability in WEBHOOK_AUTHORIZATION setting value that can result in An attacker with access to error logs could fabricate email tracking events. This att

How urgent is CVE-2018-1000089?

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

Software pages

Django vulnerabilities

Related CVEs

CVE-2018-6596 CRITICAL 9.1 UPGRADE MITIGATE webhooks/base.py in Anymail (aka django-anymail) before 1.2.1 is prone to a timing attack vulnerability on the

References

← Back to latest CVEs