Skip to main content
VulnerabilityPublished

CVE-2026-75872: maalfer MailerUp · Basic XSS

Affects maalfer MailerUpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.1.3 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade maalfer MailerUp to 1.1.3.

Affected software

ProductAffectedFixed in
maalferMailerUpAffected
  • <1.1.3
Fixed in
  • 1.1.3
GitHubMailerUppkg:github/MailerUpOther threatsAffected
  • <1.1.3
Fixed in
  • 1.1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to maalfer MailerUp version 1.1.3 or later once available, as the vulnerability affects versions before 1.1.3. Until a fix is confirmed, avoid exposing the vulnerable subscription form publicly or implement input validation and output encoding on the first_name field to prevent HTML injection.

Description

HTML Injection in the public subscription form in maalfer MailerUp before 1.1.3 allows unauthenticated remote attackers to have the application send a message carrying arbitrary HTML, to an attacker-chosen address and from the form owner's configured sending identity, via the first_name field of the subscription request, which is interpolated unescaped into the double opt-in verification email.

References

Community reviews

Loading reviews…