CVE-2026-118495 · Package
NO FIX YET · SEE WHAT TO DO
AcyMailing, a mailing-list extension for Joomla and WordPress, lets an unauthenticated attacker read a subscriber's record by knowing their email address. The record includes a per-subscriber secret key, which lets the attacker act as that subscriber, including triggering GDPR data export and account deletion where those options are enabled.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running AcyMailing versions 6.0.0 through 11.1.1 as a Joomla or WordPress extension are exposed. The attacker needs only a subscriber's email address, and the impact is strongest where GDPR export or deletion is enabled. Sites on other versions, or without AcyMailing, can skip it.
Not affected if no-acymailing, version-outside-range
Who cares acymailing, joomla, mailing-list, wordpress
6.0.0 through 11.1.1.6.0.0 through 11.1.1 are affected; the sources do not name a fixed version.Joomla / WordPress Extension - acymailing.com - Exposure of sensitive information to an unauthorized actor in AcyMailing 6.0.0 - 11.1.1 - Exposure of sensitive information to an unauthorized actor in AcyMailing 6.0.0 through 11.1.1. An unauthenticated attacker who knows a subscriber's email address can read that subscriber's record, including the per-subscriber secret key that authorises the subscription management links. Holding that key, the attacker can act as that subscriber on those endpoints, which includes triggering the GDPR data export and the GDPR account deletion where those options are enabled.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.