CVE-2018-1000089

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 events to your app. This vulnerability appears to have been fixed in v1.4.

Published: 2018-03-13 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-1000089 is rated Moderate Risk (47.6/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.32%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-1000089

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-03-30 0.63% 0.32% -0.30%
2 2025-03-29 0.32% 0.63% +0.30%
3 2025-03-17 — 0.32% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-1000089

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.4 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 5.2 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2018-1000089

GitHub Security Advisory for CVE-2018-1000089

GHSA-qh9x-mc42-vg4g · Severity: critical · Ecosystem: pip — django-anymail Includes Sensitive Information in Log Files

OS Trackers for CVE-2018-1000089

vendor priority summary link
debian not yet assigned CVE-2018-1000089 not yet assigned priority: Debian including 1 source packages (django-anymail), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2018-1000089
ubuntu medium CVE-2018-1000089 medium priority: Ubuntu including 1 source packages (django-anymail), 5 status rows across 5 suites (artful, bionic, trusty, upstream, xenial): DNE 2, ignored 1, not-affected 1, released 1. https://ubuntu.com/security/CVE-2018-1000089

Affected software / configurations for CVE-2018-1000089

Vendor Product Version Raw CPE
django-anymail_project django-anymail >= 0.2, <= 1.3 cpe:2.3:a:django-anymail_project:django-anymail:*:*:*:*:*:*:*:*

References for CVE-2018-1000089

cvelogic Threat Intelligence