dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3614

HIGH · 8.8 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 plugin for WordPress is vulnerable to privilege escalation in all versions From 9.11.0 up to, and including, 10.8.1 due to a missing capability check on the `wp_ajax_acymailing_router` AJAX handler. This makes it possible for authenticated attackers, with Subscriber-level access and above, to access admin-only controllers (including configuration management), enable the autologin feature, create a malicious newsletter subscriber with an injected `cms_id` pointing to any WordPress user, and then use the autologin URL to authenticate as that user, including administrators.

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 lacks capability validation on the wp_ajax_acymailing_router AJAX endpoint, allowing authenticated subscribers to invoke admin-only controllers. Attackers enable the autologin feature and inject a cms_id pointing to any WordPress user (including administrators) into a subscriber record, then use the autologin URL to authenticate as that user.

MitigationUpgrade AcyMailing to version 10.8.2 or later which implements proper capability checks on the AJAX router. Until then, consider restricting AJAX endpoint access via server-side rules or disabling the autologin feature.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate AcyMailing. Note the version number displayed, or check the plugin header file (usually in wp-content/plugins/acymailing/acymailing.php) for the Version: field.
    Affected if AcyMailing is installed and the version is lower than the patched version containing proper capability checks on the AJAX router.
  2. Confirm wp_ajax_acymailing_router is accessible to subscribers
    Test whether an authenticated user with Subscriber role can access the wp_ajax_acymailing_router endpoint. This can be done by sending a crafted AJAX request (with a valid nonce if required) as a subscriber-level user, or by inspecting the plugin code in wp-content/plugins/acymailing/ajax.php to verify if current_user_can() or similar capability checks exist before executing admin-only functions.
    Affected if The AJAX router endpoint executes admin-level controllers without verifying the user has administrator capabilities.
  3. Check if autologin functionality is enabled
    In AcyMailing settings, navigate to Configuration or Autologin settings (typically under AcyMailing > Configuration > Security or similar). Look for an option labeled Enable Autologin, Auto-login, or similar.
    Affected if Autologin is enabled, allowing the injection of a cms_id to generate autologin URLs for any WordPress user.
  4. Inspect user role configuration for subscribers
    In WordPress admin, go to Users > Roles or AcyMailing configuration to confirm that users with the Subscriber role have access to the acymailing_router AJAX action. Check the plugin's capability definitions in the main plugin file to see which roles are permitted to call this endpoint.
    Affected if Subscriber role users are permitted to trigger the router endpoint which creates/modifies subscriber records with arbitrary cms_id values.

A user is affected if AcyMailing is installed with a vulnerable version, the wp_ajax_acymailing_router endpoint lacks capability verification allowing subscriber-level access, and the autologin feature is enabled in the plugin configuration.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade AcyMailing to version 10.8.2 or later which implements proper capability checks on the AJAX router. Until then, consider restricting AJAX endpoint access via server-side rules or disabling the autologin feature.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3614 — 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-3614 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