CVE-2016-6893: Cross-site request forgery (CSRF) vulnerability in the user options page in GNU Mailman 2.1.x before 2.1.23 allows remote attackers to…
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 76.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: mailman (Debian:7) 1:2.1.15-1+deb7u2; mailman (Debian:8) 1:2.1.18-2+deb8u1; mailman (openSUSE:Tumbleweed) 2.1.23-1.2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to mailman (Debian:7) 1:2.1.15-1+deb7u2; mailman (Debian:8) 1:2.1.18-2+deb8u1; mailman (openSUSE:Tumbleweed) 2.1.23-1.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Cross-site request forgery (CSRF) vulnerability in the user options page in GNU Mailman 2.1.x before 2.1.23 allows remote attackers to hijack the authentication of arbitrary users for requests that modify an option, as demonstrated by gaining access to the credentials of a victim's account.
- Published
- Sep 2, 2016
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 76th percentile
- CWE
- CWE-352
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnu | mailman | cpe:2.3:a:gnu:mailman |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnu mailman2.1
- gnu mailman2.1.1
- gnu mailman2.1.10
- gnu mailman2.1.10b1
- gnu mailman2.1.10b3
- gnu mailman2.1.10b4
- gnu mailman2.1.11
- gnu mailman2.1.12
+12 more rows
- gnu mailman2.1.13
- gnu mailman2.1.14
- gnu mailman2.1.14-1
- gnu mailman2.1.15
- gnu mailman2.1.16
- gnu mailman2.1.17
- gnu mailman2.1.18
- gnu mailman2.1.18-1
- gnu mailman2.1.19
- gnu mailman2.1.2
- gnu mailman2.1.20
- gnu mailman2.1.21
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:7 | mailman | before 1:2.1.15-1+deb7u2 | 1:2.1.15-1+deb7u2 |
| Debian:8 | mailman | before 1:2.1.18-2+deb8u1 | 1:2.1.18-2+deb8u1 |
| openSUSE:Tumbleweed | mailman | before 2.1.23-1.2 | 2.1.23-1.2 |
| Red Hat:enterprise_linux:7::server | mailman | before 3:2.1.15-30.el7_9.2 | 3:2.1.15-30.el7_9.2 |
| Red Hat:enterprise_linux:7::server | mailman-debuginfo | before 3:2.1.15-30.el7_9.2 | 3:2.1.15-30.el7_9.2 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | mailman | before 2.1.15-9.6.6.1 | 2.1.15-9.6.6.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | mailman | before 2.1.15-9.6.12.1 | 2.1.15-9.6.12.1 |
| SUSE:Linux Enterprise Server 11 SP4 | mailman | before 2.1.15-9.6.3.1 | 2.1.15-9.6.3.1 |
| SUSE:OpenStack Cloud 7 | mailman | before 2.1.17-3.3.3 | 2.1.17-3.3.3 |
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-44227In GNU Mailman before 2.1.38, a list member or moderator can get a CSRF token and craft an admin request (using that token) to set a new…35Monitor
- CVE-2016-7123Cross-site request forgery (CSRF) vulnerability in the admin web interface in GNU Mailman before 2.1.15 allows remote attackers to hijack…35Monitor
- CVE-2025-43920GNU Mailman 2.1.39, as bundled in cPanel (and WHM), in certain external archiver configurations, allows unauthenticated attackers to…32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2011-5024Dec 29, 2011 · Cross-site scripting (XSS) vulnerability in mmsearch/design in the Mailman/htdig integration patch for Mailman allows remote attackers to…17Monitor
- ← EarlierCVE-2015-2775Apr 13, 2015 · Directory traversal vulnerability in GNU Mailman before 2.1.20, when not using a static alias, allows remote attackers to execute arbitrary…32Monitor
- Later →CVE-2018-5950Jan 23, 2018 · Cross-site scripting (XSS) vulnerability in the web UI in Mailman before 2.1.26 allows remote attackers to inject arbitrary web script or…25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:mailman | 1:2.1.15-1+deb7u2 · Debian:7 | Package registry (OSV) |
| opensuse:mailman | 2.1.23-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:mailman | 3:2.1.15-30.el7_9.2 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:mailman-debuginfo | 3:2.1.15-30.el7_9.2 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| suse:mailman | 2.1.15-9.6.3.1 · SUSE:Linux Enterprise Server 11 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0970 · Dec 6, 2021(RedHat Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.