dbcve.org
12 Step Meeting ListWordPress extension · Code4recovery

CVE-2024-22296

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 3.14.29 or later.
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
Missing Authorization vulnerability in Code for Recovery 12 Step Meeting List.This issue affects 12 Step Meeting List: from n/a through 3.14.28.

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. The CVSS score of 8.8 indicates a serious access control weakness that allows unauthenticated or improperly authorized users to perform actions they should not have permission to perform. The specific endpoint or function affected is not detailed in available sources.

MitigationApply the vendor patch/update to version 3.14.29 or later once available. In the interim, restrict access to the affected plugin endpoints via web server configuration or implement additional access controls at the application layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
12 Step Meeting ListWordPress extension
Affected:< 3.14.29

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 the 12 Step Meeting List plugin is installed
    Navigate to WordPress admin > Plugins and locate '12 Step Meeting List' by Code4recovery in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In WordPress admin > Plugins, click on the plugin details to view the installed version number, or inspect the plugin main file header in wp-content/plugins/12-step-meeting-list
    Affected if The installed version is lower than 3.14.29
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that the '12 Step Meeting List' plugin shows as 'Active'
    Affected if The plugin is active and the version is below 3.14.29
  4. Inspect plugin endpoints for access control gaps
    Review the plugin directory for PHP files handling admin or public actions, specifically looking for functions that process form submissions, data exports, or meeting list modifications without capability checks
    Affected if The plugin version is below 3.14.29 and exposes endpoints that lack proper authorization checks

A user is affected if the Code4recovery 12 Step Meeting List plugin is installed, active, and running a version lower than 3.14.29, as this version range contains the missing authorization vulnerability.

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
Upgrade available Upgrade to 3.14.29 or later
Fixed in 3.14.29
Interim mitigation

Apply the vendor patch/update to version 3.14.29 or later once available. In the interim, restrict access to the affected plugin endpoints via web server configuration or implement additional access controls at the application layer.

Recommended fix High confidence

Version 3.14.29 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the '12 Step Meeting List' plugin
  4. Check if the current version is below 3.14.29
  5. If vulnerable, click 'Update Now' to install version 3.14.29 or later
  6. Verify the update was successful by checking the plugin version after update

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

Fix this in 12 Step Meeting List Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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