dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-5200

HIGH · 8.8 CVSS v3.1 Published 2026-05-20
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 – An Ultimate Newsletter Plugin and Marketing Automation Solution for WordPress plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 10.8.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify privileged AcyMailing configuration, export subscriber secret keys, and chain these actions into administrator account takeover when a target administrator email address is known.

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 fails to properly verify user authorization before allowing configuration modifications. Authenticated users with subscriber-level permissions (the lowest WordPress role) can modify privileged settings, export subscriber secret keys, and leverage these actions to take over administrator accounts when the target admin email is known.

MitigationUpdate to a patched version of AcyMailing when available; in the interim, audit user roles and remove unnecessary subscriber-level capabilities or disable subscriber accounts if not required.

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. Confirm AcyMailing plugin is installed
    Navigate to WordPress admin > Plugins and look for AcyMailing in the installed plugins list, or check the wp-content/plugins/ directory for an acymailing folder
    Affected if The AcyMailing plugin is present in the WordPress installation
  2. Identify installed AcyMailing version
    In WordPress admin, go to Plugins > Installed Plugins > AcyMailing and note the version number displayed, or read the main plugin PHP file header for the Version field
    Affected if The installed version is 10.8.2 or earlier (or an unspecified version lacking the authorization fix)
  3. Audit subscriber-level user accounts
    In WordPress admin, go to Users and review all accounts with the Subscriber role; also check if any AcyMailing-specific user roles exist with elevated permissions
    Affected if There are subscriber-level users in the system who should not have administrative access
  4. Check configuration write access for subscribers
    Attempt to access AcyMailing configuration settings (typically at /wp-admin/admin.php?page=acymailing_configuration) using a test subscriber account, or inspect the capability checks in the plugin's configuration controller files
    Affected if A subscriber-level user can modify plugin configuration settings without proper admin privileges
  5. Verify secret key exposure risk
    Review AcyMailing export functions and API settings for any endpoints that allow subscribers to export or access subscriber secret keys, or check if any export files are accessible to lower-privileged users
    Affected if Subscribers can export or view subscriber secret keys through the plugin interface

A user is affected if AcyMailing is installed with any version at or below 10.8.2 AND there exist subscriber-level accounts that could exploit missing authorization checks to modify settings or access sensitive data.

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 to a patched version of AcyMailing when available; in the interim, audit user roles and remove unnecessary subscriber-level capabilities or disable subscriber accounts if not required.

Recommended fix Moderate confidence

AcyMailing version 10.8.3 or later

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to Dashboard > Plugins in your WordPress admin panel.
  3. 3. Locate the AcyMailing plugin in the installed plugins list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. After updating, verify the plugin is running on version 10.8.3 or later.
  6. 6. Review user roles and permissions to ensure no unauthorized changes were made during the vulnerability window.
  7. 7. Consider resetting sensitive credentials for any administrators who may have been targeted.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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