AcyMailing 11.1.2 addresses seven published CVEs affecting releases through 11.1.1, including two High-rated CVSS 4.0 issues scored 8.8 by the Joomla CNA. Joomla administrators should update promptly, verify the installed version, and review subscriber, campaign and access-controlled content settings.
AcyMailing 11.1.2 is a security update for a set of front-end authorization and information-exposure weaknesses. The published records cover seven CVEs. Some can be reached without authentication, making timely patching appropriate for Joomla sites that use AcyMailing for newsletters, subscription management or restricted communications.
What AcyMailing 11.1.2 fixes
The seven issues affect AcyMailing versions up to and including 11.1.1. The documented fixed version is 11.1.2; administrators should deploy 11.1.2 or a later available release rather than assume that an earlier update contains part of the fix set.
The vulnerabilities concern authorization checks, exposure of subscriber or campaign information, and redirect handling. They are front-end accessible in the sense that the affected functions are exposed through site-facing features. That does not mean they are all identical: six records describe unauthenticated scenarios, while one requires an authenticated user.
The platform scope also matters. Five CVEs affect AcyMailing for both Joomla and WordPress. Two—CVE-2026-120468 and CVE-2026-120471—affect the Joomla extension only; the published records explicitly state that the WordPress plugin is not affected by those two issues.
This is not a report of remote code execution or SQL injection. Neither type of vulnerability is described in the supplied CVE records. The immediate concern is protection of subscriber data, mailing-list configuration, campaign visibility, subscription preferences and Joomla access-controlled content.
Joomla extension vulnerabilities at a glance
The following summary is based on the Joomla CNA CVE records. CVSS figures shown are CVSS 4.0 scores. No CVSS 3.1 scores are currently provided for these entries, so the values must not be read as CVSS 3.1 ratings.
| Extension scope | CVE | Authentication | Affected versions | Recommended version | CVSS 4.0 | KEV status |
|---|---|---|---|---|---|---|
| Joomla and WordPress | CVE-2026-118495 | None | 6.0.0 through 11.1.1 | 11.1.2 or later | 8.8 High | Not listed |
| Joomla and WordPress | CVE-2026-120466 | None | 1.0.0 through 11.1.1 | 11.1.2 or later | 8.8 High | Not listed |
| Joomla and WordPress | CVE-2026-120467 | Required | 1.0.0 through 11.1.1 | 11.1.2 or later | 7.1 High | Not listed |
| Joomla only | CVE-2026-120468 | None | 1.0.0 through 11.1.1 | 11.1.2 or later | 6.9 Medium | Not listed |
| Joomla and WordPress | CVE-2026-120469 | None | 1.0.0 through 11.1.1 | 11.1.2 or later | 5.1 Medium | Not listed |
| Joomla and WordPress | CVE-2026-120470 | None | 1.0.0 through 11.1.1 | 11.1.2 or later | 6.9 Medium | Not listed |
| Joomla only | CVE-2026-120471 | None | 1.0.0 through 11.1.1 | 11.1.2 or later | 6.9 Medium | Not listed |
“Not listed” means none of the seven CVEs is currently in the CISA Known Exploited Vulnerabilities catalog according to the reviewed evidence. Authoritative sources have not confirmed exploitation in the wild. That status should not delay routine security maintenance: CVSS expresses assessed technical severity, while KEV inclusion reflects known exploitation. They answer different questions.
The two 8.8-rated issues
The highest scores in this group belong to CVE-2026-118495 and CVE-2026-120466. Each has an official CVSS 4.0 score of 8.8, rated High, in the Joomla CNA data.
Subscriber record and secret-key exposure
CVE-2026-118495 affects AcyMailing 6.0.0 through 11.1.1 on Joomla and WordPress. The record states that an unauthenticated party who knows a subscriber email address can read that subscriber’s record, including the per-subscriber secret key used for subscription-management links. Possession of that key can allow actions as that subscriber on those management functions, including data export or account deletion where those features are enabled.
For Joomla site owners, this makes the update more than a routine extension upgrade. After patching, review whether existing subscription-management links should be invalidated or rotated where that is operationally feasible, especially for lists holding personal, client, member or employee data.
Unauthorised subscription changes
CVE-2026-120466 affects versions 1.0.0 through 11.1.1 on both platforms. An unauthenticated party who knows a subscriber’s email address can unsubscribe that person from one or all lists without demonstrating ownership of the address. The record also describes the ability to test whether a supplied address is subscribed on the site.
Administrators should examine recent unsubscribe activity after the upgrade. Unusual clusters of unsubscribes, repeated changes involving particular lists, or unexpected complaints from subscribers deserve follow-up. Retain relevant application and web-server logs in line with the site’s normal incident-handling process.
The remaining five CVEs and their Joomla impact
CVE-2026-120467 is an authenticated issue affecting Joomla and WordPress releases 1.0.0 through 11.1.1. A logged-in user can subscribe or unsubscribe another subscriber because the subscriber identity is not properly tied to the record being changed. Review who can access subscription-management functions and confirm that accounts have only the permissions they require.
CVE-2026-120468 is Joomla-only. In affected Joomla extension versions, an unauthenticated visitor can enumerate mailing lists, including non-public and access-restricted lists, and obtain metadata such as descriptions, access levels, owning users and subscriber counts. This can reveal organisational information even where list contents are not disclosed. Review restricted lists and remove sensitive details from names and descriptions where possible.
CVE-2026-120469 affects both Joomla and WordPress. Subscription and unsubscription functions can be used in links that redirect a visitor to an arbitrary external destination. The practical risk is phishing: recipients may trust a link because it begins on a familiar site. After applying the update, check custom campaign templates and subscription workflows for redirect-dependent behaviour, and use only expected destinations in future content.
CVE-2026-120470 affects both platforms. It permits unauthenticated access to online versions of campaigns that were not made public, including campaigns later unpublished and campaigns sent to restricted audiences. Review campaigns that contained confidential announcements, member-only information or personal data, and assess whether the content requires a separate response under your organisation’s privacy and communications procedures.
CVE-2026-120471 is the second Joomla-only issue. It can cause a site module to render without respecting its configured Joomla access level, exposing material intended for higher view levels. Audit modules connected to AcyMailing workflows, particularly those used for member, customer, staff or other restricted audiences.
Prioritised update and verification checklist
AcyMailing installations should be brought to 11.1.2 or later as soon as practical. Agencies and hosts should treat this as a fleet-management task: identify every Joomla and WordPress installation using AcyMailing, including low-traffic, staging and client-owned sites that may not receive routine attention.
- Inventory the installation. Confirm whether AcyMailing is installed and record its version before making changes. Versions through 11.1.1 fall within the documented affected ranges.
- Back up according to your established change process. Preserve a recoverable site and database backup before extension maintenance, particularly where newsletter configuration and subscriber records are business-critical.
- Update to 11.1.2 or later. Obtain the current package or update information from the AcyMailing website or the normal extension update path.
- Verify the deployed version in the administration interface. Do not rely only on a completed update message. Confirm that the Joomla component reports 11.1.2 or later. This is particularly useful on sites whose update-site configuration may have been altered or lost.
- Test normal subscriber journeys. Validate legitimate sign-up, unsubscribe and preference-management processes with approved test accounts. Confirm that routine mailings and any custom templates still behave as intended.
- Review exposure settings. Check mailing-list descriptions, subscription-management settings, online campaign visibility, and AcyMailing-related Joomla modules with non-public access levels.
- Monitor after deployment. Look for unusual unsubscribe patterns and unexpected access to online campaign views. Escalate findings through the site’s established security and privacy processes.
If an urgent update cannot be completed immediately, reduce exposure by limiting sensitive information in list metadata, reviewing restricted modules, and avoiding publication of sensitive campaign content through online-view workflows. These are temporary risk-reduction measures, not substitutes for the fixed release.
How to interpret the CVE and NVD status
The technical descriptions and scores in this article rely on the Joomla CNA CVE records. At the time of review, the NVD records show Awaiting Analysis for CVE-2026-118495, CVE-2026-120466, CVE-2026-120468, CVE-2026-120469, CVE-2026-120470 and CVE-2026-120471. CVE-2026-120467 is marked Deferred. Those statuses mean NVD has not completed its own analysis; they do not invalidate the published Joomla CNA records.
For administrators, the useful distinction is straightforward. A CVSS 4.0 score helps prioritise a weakness by its assessed characteristics. Inclusion in CISA KEV would indicate known exploitation tracked by that catalog. These seven CVEs are not currently listed in KEV, and there is no authoritative confirmation of exploitation. The absence of confirmed exploitation should be reported accurately, but it is not a reason to leave known affected versions exposed.
Operational notes for Joomla teams and agencies
For a single site, the main task is a controlled update followed by verification of newsletter and restricted-content behaviour. For agencies, the same issue also tests asset inventory: client sites often use email extensions long after the original implementation has been forgotten.
- Maintain an inventory that maps each client site to its installed extensions and their versions.
- Separate Joomla-only findings from cross-platform findings in client communications. CVE-2026-120468 and CVE-2026-120471 do not apply to the WordPress plugin.
- Document the installed version after remediation and the date on which normal subscription workflows were tested.
- Discuss potentially sensitive historical campaigns with the data owner before deciding whether a privacy review is required.
- Use least-privilege access for staff accounts that manage subscribers, lists and campaigns; this is especially relevant to the authenticated CVE-2026-120467.
The central conclusion is practical rather than alarmist: AcyMailing 11.1.2 is the documented remediation release for all seven CVEs. Update every affected Joomla installation, verify the version, and review the site-facing features that manage subscriber information and restricted communications.
Add comment