dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-12170

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The AcyMailing – An Ultimate Newsletter Plugin and Marketing Automation Solution for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'alignment' attribute in all versions up to, and including, 10.10.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The AcyMailing WordPress plugin versions up to 10.10.2 contain a stored XSS vulnerability in the 'alignment' attribute. Authenticated users with contributor-level permissions can inject malicious scripts through insufficient input sanitization, which executes when other users access affected pages.

MitigationUpdate the plugin to version 10.10.3 or later. If immediate update is not possible, implement input sanitization using sanitize_text_field() and output escaping with esc_attr() for the alignment attribute throughout the codebase.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AcyMailing plugin is installed and check its version
    Log into WordPress admin, go to Plugins > Installed Plugins, locate AcyMailing, and note the version number displayed. Alternatively, check the main plugin file (for example, acymailing.php) for the 'Version' header using a file manager or FTP.
    Affected if The installed version is 10.10.2 or earlier.
  2. Confirm user role with contributor-level access exists
    Navigate to Users > All Users in WordPress admin. Review the roles assigned to each user. Identify any user with the 'Contributor', 'Author', 'Editor', or 'Administrator' role.
    Affected if At least one user account has contributor-level permissions or higher.
  3. Inspect the alignment attribute handling in plugin code
    Access the AcyMailing plugin files via FTP or file manager. Search for files that process the 'alignment' attribute, typically in frontend display or configuration files. Look for code that outputs this attribute without proper sanitization.
    Affected if The alignment attribute is output in HTML without sanitize_text_field() or esc_attr() applied to the value.
  4. Check database or configuration for stored alignment values
    Use a database tool (like phpMyAdmin) to inspect the AcyMailing database tables. Look for records containing the alignment field that may contain script tags or unusual characters.
    Affected if Records in the database contain unescaped HTML or JavaScript within alignment fields.

A user is affected if AcyMailing version 10.10.2 or earlier is installed, contributor-level users exist, and the alignment attribute in the plugin outputs unsanitized input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 10.10.3 or later. If immediate update is not possible, implement input sanitization using sanitize_text_field() and output escaping with esc_attr() for the alignment attribute throughout the codebase.

Recommended fix Moderate confidence

Upgrade to AcyMailing version 10.10.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the AcyMailing plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update completes successfully
  6. 6. Test the plugin functionality to ensure the upgrade did not break any newsletter or email automation features
Caveat Review plugin settings and test email campaigns after upgrading to ensure compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12170 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data