dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39569

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in AA Web Servant 12 Step Meeting List 12-step-meeting-list allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects 12 Step Meeting List: from n/a through <= 3.19.9.

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 · moderate confidence

Missing authorization vulnerability in the 12 Step Meeting List WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to sensitive functionality, potentially permitting unauthenticated or lower-privileged users to perform actions intended for administrators.

MitigationImplement proper authorization checks across all sensitive functions and update to the latest patched version when available. Review and correct access control security level configurations to ensure proper permission validation.

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
None
Availability
None

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

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 the 12 Step Meeting List plugin is installed
    Check for the plugin directory at wp-content/plugins/12-step-meeting-list/ or search for '12-step-meeting-list' in the WordPress plugins folder via file system or FTP
    Affected if The plugin directory exists in the WordPress installation
  2. Determine the installed plugin version
    Open the plugin's main PHP file (usually within the plugin directory) and locate the 'Version' header comment in the file's plugin metadata, or check the readme.txt file for the version number
    Affected if The version listed is 3.19.9 or any version lower than 3.19.9
  3. Confirm WordPress user roles are present
    Log into the WordPress admin dashboard and navigate to Users > All Users to review existing user accounts and their assigned roles
    Affected if There are users with roles other than Administrator (such as Editor, Author, Subscriber, or custom roles) who could potentially access the vulnerable functions
  4. Test for unauthenticated access to meeting data
    Use a browser or HTTP tool (curl) to access the plugin's public meeting list endpoint or AJAX actions without logging in, observing whether sensitive meeting information or administrative functions are returned without requiring authentication
    Affected if Meeting data, attendee information, or administrative functions are accessible without authentication or with a low-privilege user account

A user is affected if the 12 Step Meeting List plugin version is 3.19.9 or lower and the plugin is active, with low-privilege or unauthenticated users able to access data or functions that should require higher permissions.

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

Implement proper authorization checks across all sensitive functions and update to the latest patched version when available. Review and correct access control security level configurations to ensure proper permission validation.

Recommended fix High confidence

Version 3.20.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find "12 Step Meeting List" by AA Web Servant
  4. Check if the current version is 3.19.9 or earlier
  5. If vulnerable, click "Update Now" to upgrade to the latest version
  6. Verify the update completed successfully and the plugin is now at version 3.20.0 or later
  7. Test that the plugin functionality works as expected after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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