CVE-2026-102562

AcyMailing <= 11.1.0 - Unauthenticated Stored Cross-Site Scripting via 'customField[]' Parameter

Published Oct 13, 2026 CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The AcyMailing plugin for WordPress contains a stored cross‑site scripting vulnerability that originates from the customField[] parameter of the publicly accessible frontusers::subscribe endpoint. Because the plugin's input sanitizer does not properly strip or encode HTML, an attacker can embed malicious JavaScript into a subscriber field that is later inserted unencoded into the mail body and the archive view. When any user, including administrators, views the online‑archive page for that subscriber, the script runs in the visitor’s browser, enabling arbitrary script execution in the context of that page. This flaw corresponds to CWE‑79.

Affected Systems

The affected product is AcyMailing, the Ultimate Newsletter Plugin and Marketing Automation Solution for WordPress from acyba. Versions up to and including 11.1.0 are vulnerable. Any installation of these versions that keeps the public frontusers::subscribe endpoint active is susceptible, regardless of the underlying WordPress version.

Risk and Exploitability

The CVSS base score of 7.2 places this flaw in the high‑severity range. Attackers need only unauthenticated access to post data to the frontusers::subscribe endpoint; no authentication or elevated privileges are required. Once a malicious value is stored, it is rendered whenever a user loads the subscriber’s archive page, including privileged administrators who click the link generated in the Subscribers → History screen. The exploitation path is straightforward, and the flaw is not listed in CISA's KEV catalog, while an EPSS score is not available. The high impact to privileged users makes this vulnerability a significant threat to affected sites.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest AcyMailing release that removes the unsanitized handling of customField[] and corrects archive view rendering.
  • If an upgrade cannot be performed immediately, block or disable external access to the frontusers::subscribe endpoint or strip the customField[] parameter from incoming requests.
  • As a temporary measure, apply output encoding (e.g., using WordPress functions such as wp_kses() or sanitize_text_field()) to any stored customField[] values before they are displayed in the archive view, ensuring that embedded scripts are neutralized.

Generated by OpenCVE AI on October 13, 2026 at 10:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Acyba
Acyba acymailing
Wordpress-extensions
Wordpress-extensions acymailing
Vendors & Products Acyba
Acyba acymailing
Wordpress-extensions
Wordpress-extensions acymailing
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title AcyMailing <= 11.1.0 - Unauthenticated Stored Cross-Site Scripting via 'customField[]' Parameter
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Oct 15, 2026, 4:43 PM
Reserved
Sep 29, 2026, 1:32 PM
Status
Deferred
Published
Oct 13, 2026, 8:16 AM
Modified
Oct 15, 2026, 5:17 PM