VYPR
← All advisories
Unrated severityNVD Advisory· Published Jul 26, 2018· Updated Aug 5, 2024

CVE-2018-0618

CVE-2018-0618

Description

Mailman 2.1.26 and earlier contains a stored cross-site scripting vulnerability allowing authenticated attackers to inject arbitrary web scripts.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Mailman 2.1.26 and earlier contains a stored cross-site scripting vulnerability allowing authenticated attackers to inject arbitrary web scripts.

Vulnerability

Mailman versions 2.1.26 and earlier are affected by a stored cross-site scripting (XSS) vulnerability (CWE-79). The flaw resides in the web interface and can be triggered via unspecified vectors, allowing injection of arbitrary HTML or JavaScript. [1][2]

Exploitation

An attacker must be a remote authenticated user of the Mailman web interface. The exact input vectors are not publicly detailed, but the vulnerability is stored, meaning the injected script persists and executes when other users view the affected page. [1]

Impact

Successful exploitation allows the attacker to execute arbitrary scripts in the context of a victim's browser. This can lead to session hijacking, defacement, or theft of sensitive information displayed in the web interface. [1]

Mitigation

Upgrade to Mailman 2.1.27 or later, which was released on June 22, 2018. [3] Distributions such as Ubuntu (via USN-4348-1) and Gentoo (via GLSA 201904-10) have provided updated packages. [2][4] No workaround is available; upgrading is the only solution. [4]

References
  1. Mailman vulnerable to cross-site scripting
  2. USN-4348-1: Mailman vulnerabilities | Ubuntu security notices | Ubuntu
  3. [Mailman-Announce] Mailman 2.1.27 released
  4. Multiple vulnerabilities (GLSA 201904-10) — Gentoo security

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

19

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

6

News mentions

0

No linked articles in our index yet.