The AcyMailing plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the…

Why it is Yellow

• CVSS 7.2 high
• Remotely exploitable without logging in

References

• https://plugins.trac.wordpress.org/browser/acymailing/tags/11.1.0/back/Classes/FieldClass.php#L292
• https://plugins.trac.wordpress.org/browser/acymailing/tags/11.1.0/back/Classes/UserClass.php#L1187
• https://plugins.trac.wordpress.org/browser/acymailing/tags/11.1.0/back/Core/wordpress/security.php#L122
• https://plugins.trac.wordpress.org/browser/acymailing/tags/11.1.0/back/dynamics/subscriber/SubscriberInsertion.php#L159
• https://plugins.trac.wordpress.org/browser/acymailing/tags/11.1.0/front/FrontControllers/FrontusersController.php#L69
• https://plugins.trac.wordpress.org/browser/acymailing/tags/11.1.0/front/FrontViews/Archive/tmpl/view.php#L17
• https://plugins.trac.wordpress.org/changeset?reponame=&old=3729031%40acymailing&new=3729031%40acymailing
• https://www.wordfence.com/threat-intel/vulnerabilities/id/eb8f03fb-d1af-4727-87d7-58dbe4013d8a?source=cve

Original description

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.