CVE-2026-102562 json
AcyMailing <= 11.1.0 - Unauthenticated Stored Cross-Site Scripting via 'customField[]' Parameter
published 27d ago modified 25d ago also EUVD-2026-98346
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
The AcyMailing plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the customField[] parameter of the public frontusers::subscribe endpoint in versions up to, and including, 11.1.0. This is due to insufficient input sanitization and output escaping in the acym_cleanVar() sanitizer, whose HTML-tag stripper only matches complete tags (requiring a closing '>'), together with SubscriberInsertion::replaceUserInformation() and the archive view template, which substitute the stored subscriber field value into the mail body and emit it without HTML encoding. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses the online-archive URL for the poisoned subscriber, including administrators who click the plugin-generated link in the Subscribers → History screen.
Is CVE-2026-102562 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 25d ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- acyba AcyMailing – An Ultimate Newsletter Plugin and Marketing Automation Solution for WordPress
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/eb8f03fb-d1af-4727-87d7-58dbe4013d8a?source=cve
- plugins.trac.wordpress.org /browser/acymailing/tags/11.1.0/front/FrontViews/Archive/tmpl/view.php#L17
- plugins.trac.wordpress.org /browser/acymailing/tags/11.1.0/back/dynamics/subscriber/SubscriberInsertion.php#L159
- plugins.trac.wordpress.org /browser/acymailing/tags/11.1.0/back/Classes/FieldClass.php#L292
- plugins.trac.wordpress.org /browser/acymailing/tags/11.1.0/back/Core/wordpress/security.php#L122
- plugins.trac.wordpress.org /browser/acymailing/tags/11.1.0/back/Classes/UserClass.php#L1187
- plugins.trac.wordpress.org /browser/acymailing/tags/11.1.0/front/FrontControllers/FrontusersController.php#L69
- plugins.trac.wordpress.org /changeset?reponame=&old=3729031%40acymailing&new=3729031%40acymailing
Sources
- CVE List CVE-2026-102562
- NVD CVE-2026-102562
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.