top of page

AcyMailing CVE-2026-120468 Is Being Exploited, per VulnCheck. It Is the Mildest of Seven Flaws Fixed on November 12. Update to 11.1.2

Writer: Patrick Duggan
Patrick Duggan
18 minutes ago
5 min read

If you run AcyMailing on a Joomla or WordPress site, update it to version 11.1.2 or later today. On November 15, VulnCheck added CVE-2026-120468, a flaw in AcyMailing for Joomla, to its Known Exploited Vulnerabilities list on the strength of its own canary sensors. That flaw is the mildest of seven that AcyMailing fixed in one release on November 12. The same update closes a High-rated flaw, CVE-2026-118495, that lets anyone who knows a subscriber's email address read that subscriber's record and secret key, on Joomla and WordPress alike. Anyone already probing AcyMailing sites has the newer flaws in the same changelog. The vendor says no setting protects an older version from either one.





What is confirmed


The exploited flaw. CVE-2026-120468 lets an anonymous visitor pull every mailing list on a Joomla site that runs AcyMailing, including lists marked as not visible and lists restricted to a Joomla access level, with each list's name, description, owner and subscriber count. The vendor's advisory explains the bug: a front-end endpoint that fills list pickers applied its access filter only when it could identify the user asking, and for an anonymous caller it skipped the filter instead of refusing. The vendor says subscriber email addresses were not returned, so what leaked is the structure of your lists, not their contents. The WordPress plugin does not ship the affected code.


The vendor rates it 6.9, Medium (CVSS 4.0). The CVE record, published by the Joomla Project as the numbering authority, says AcyMailing 1.0.0 through 11.1.1 is affected; the vendor's own advisory says 6.0.0 through 11.1.1. Either way, 11.1.2 is the fix. Phil Taylor of mySites.guru reported it on October 7.


The exploitation claim, and what its date means. VulnCheck's KEV entry, which we read through VulnCheck's API, marks CVE-2026-120468 as reported exploited by VulnCheck's canaries, with a single exploitation reference dated November 15 and a date_added of November 15. VulnCheck sets date_added to its earliest evidence of exploitation, not to the moment the entry appeared on its list. Here the two coincide on the same Sunday, three days after the fix and CVE went public. Earlier, at 21:33 UTC on November 12, CISA's enrichment on the CVE record had marked exploitation as "none", which was true of what anyone knew then.


Not in CISA's catalog. CVE-2026-120468 is not in CISA's Known Exploited Vulnerabilities catalog as of its latest release, version 2026.11.13 from Friday, November 13, which lists 1,781 entries. So there is no federal due date. None of the other six AcyMailing CVEs is in VulnCheck's KEV either.


The other six. The same November 12 release, 11.1.2, carries six more security fixes, each with its own CVE:


  • CVE-2026-118495, High, 8.8. Anyone who knew a subscriber's email address could read that subscriber's whole record, including the per-subscriber key that authorizes subscription management links. With that key an attacker can act as the subscriber, including the GDPR export and deletion tasks where a site enables them. Joomla and WordPress. Reported independently by two researchers through Ghent University's disclosure program.

  • CVE-2026-120466, High. Depending on a setting, an anonymous visitor could unsubscribe anyone whose email address they knew.

  • CVE-2026-120467, High. Any logged-in user could subscribe or unsubscribe any other subscriber.

  • CVE-2026-120469, Medium. Redirects after subscribing did not check the destination domain, an open redirect.

  • CVE-2026-120470, Medium. The online version of a campaign could be opened without permission, including campaigns never made public.

  • CVE-2026-120471, Medium. A site module could be shown to a visitor outside its access level, on Joomla.

The severities and descriptions of the last five come from the vendor's changelog; we read the full advisories for CVE-2026-120468 and CVE-2026-118495 only.



What is not known


  • Who is exploiting it, from where, and how often. VulnCheck's canary records, which would hold the source addresses and request counts, require a subscription we do not have. We know the date of the earliest sighting and nothing about the traffic.

  • Whether any real site was hit. A canary sighting means someone sent the exploit request at a decoy. It does not tell us that a production site lost its list structure, and we do not claim that.

  • Whether the High-rated flaws are being exploited. No source we read says so. They are newer to the public than the flaw that is, and they share its target list, which is the reason to patch them together.

  • How many sites run AcyMailing. WordPress.org reports 5,000+ active installs for the WordPress plugin, a bucket rather than a count, and that plugin is not affected by CVE-2026-120468 itself. We found no count for the Joomla extension.

  • Public exploit code. Our exploit harvester holds no public proof-of-concept repository for CVE-2026-120468.


What to do


  1. Update AcyMailing to 11.1.2 or later, on Joomla and on WordPress. The vendor says no configuration mitigates CVE-2026-120468 or CVE-2026-118495 on an older version. WordPress.org shows 11.1.2 as the current plugin version, published November 12.

  2. Search your web server access log for requests carrying the loadEntityFront task from addresses that are not yours, in the period before you updated. That is the request pattern the vendor gives for CVE-2026-120468. Any hit means someone read your list structure, not your subscribers.

  3. Read the subscriber history in AcyMailing's administration for CVE-2026-118495. The vendor says that flaw has no distinct signature: look for repeated subscription actions against many different addresses from one IP. Their absence proves nothing, because reading a record does not always create an entry.

  4. If your site enables GDPR export or deletion, review those actions in the same history for the period before you updated. A stolen subscriber key can trigger them.

  5. If you host sites for others, check every Joomla install for the com_acym component, not only the ones you remember adding it to.


How we know


We read, on November 16: the CVE record for CVE-2026-120468 from the CVE Services API, its NVD entry (status "Awaiting Analysis", published November 12 at 18:17 UTC), the AcyMailing changelog for 11.1.2, AcyMailing's advisories for CVE-2026-120468 and CVE-2026-118495, VulnCheck's KEV entries for all seven CVEs through its API, the CISA KEV JSON feed (catalog 2026.11.13), and the WordPress.org plugin record. No press report was needed; every claim above comes from those primary sources.


Our edge instruments watch HTTP traffic to our own web properties, and we run no Joomla site and no Joomla decoy. Across 444,104 edge-block records, 75,829 edge-canary records and 1,855 origin-honeypot records since October 1, none matched loadEntityFront, com_acym or acymailing. That zero is a measurement of our own zones, which an attacker hunting Joomla installs has little reason to probe; it says nothing about scanning of real AcyMailing sites.


This post is coverage, not a detection lead. VulnCheck's canaries saw the exploitation; we did not.



Indicators


None published in the sources we read. We added nothing to our feed for this story.



Sources


If this was useful, or if it wasn't, the rating widget below takes ten seconds and is the only way we know.




Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.


Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page