CVE-2026-75872: HTML Injection in MailerUp double opt-in verification email

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by Secur0, published 2026-08-18).

Weakness: CWE-80 Improper neutralization of Script-Related HTML tags in a web page (basic XSS)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality none, integrity low, availability none. 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

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS
0.007
low predicted chance of attack
VEDAS
0.988
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
maalfer MailerUpbefore 1.1.3Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: 1.1.3.

Vendor guidance:

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-75872 MailerUp - HTML Injection via subscription first_name. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-75872 MailerUp - HTML Injection via subscription first_name"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/subscribe/"; nocase; fast_pattern; http.request_body; content:"first_name"; nocase; pcre:"/first_name[\x22'=:\s]{0,6}[^&,}\r\n]{0,120}(%3c|<)\s*\/?[a-z!]/i"; classtype:web-application-attack; reference:cve,CVE-2026-75872; reference:url,https://www.exploit.observer/?keyword=CVE-2026-75872&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=mailerup&match=exact; metadata:signature_type network_only; sid:1079207; rev:1;)

CVE-2026-75872.rules on GitHub

References

Vendor advisories and patches

Technical analysis and advisories

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust