dbcve.org
AiomaticWordPress extension · Coderevolution

CVE-2024-13816

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-08
Fix available
A fix is available. Upgrade to 2.3.7 or later.
See remediation →
60/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
The Aiomatic - Automatic AI Content Writer & Editor, GPT-3 & GPT-4, ChatGPT ChatBot & AI Toolkit plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to a missing capability checks on multiple functions in all versions up to, and including, 2.3.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update and delete posts, list and delete batches, list assistant uploaded files, delete personas, delete forms, delete templates, and clear logs. The vulnerability was partially patched in version 2.3.5.

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 Aiomatic WordPress plugin versions up to 2.3.6 lack proper capability checks on multiple admin functions, allowing authenticated users with Subscriber-level privileges (the lowest WordPress role) to perform destructive actions including updating/deleting posts, deleting batches, files, personas, forms, templates, and clearing logs. This is a Broken Access Control vulnerability where functions trust user input without verifying authorization.

MitigationUpgrade to the latest version of the Aiomatic plugin (currently 2.3.6 according to the description; verify patch status with vendor) and audit all functions for proper current_user_can() capability checks. Restrict the Subscriber role permissions until the patch is verified.

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
AiomaticWordPress extension
Affected:< 2.3.7

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Confirm Aiomatic plugin installation and version
    Check the plugin file header in wp-content/plugins/aiomatic-automatic-ai-content-writer/aiomatic.php or view the installed plugins list in WordPress admin under Plugins. Look for the version number in the plugin header comment.
    Affected if The installed version is below 2.3.7 (e.g., 2.3.6, 2.3.5, etc.) or the version cannot be determined but the plugin is present.
  2. Identify WordPress user roles with Subscriber access
    Navigate to WordPress admin Users > All Users and review the Role column. Alternatively, query the wp_usermeta table for users with wp_capabilities meta containing 'subscriber'.
    Affected if Any user account exists with the Subscriber role assigned.
  3. Verify AJAX action accessibility without capability checks
    Test whether AJAX actions related to Aiomatic (check admin-ajax.php for actions like aiomatic_delete, aiomatic_update_post, aiomatic_clear_logs, aiomatic_delete_batch) respond to requests from a low-privilege user. Use a Subscriber-level account to attempt these actions via curl or browser developer tools.
    Affected if The AJAX endpoints process requests from Subscriber-level users without returning a capability error or requiring higher privileges.
  4. Inspect plugin source code for capability checks
    Examine the main plugin PHP file for functions handling destructive actions (deleting posts, batches, files, personas, forms, templates, clearing logs). Search for presence of 'current_user_can' or capability verification before executing the action.
    Affected if The plugin code lacks current_user_can() calls or equivalent authorization checks before executing sensitive operations.

A user is affected if the Aiomatic plugin version is below 2.3.7 AND any Subscriber-level user exists in WordPress AND the plugin's sensitive functions are accessible without proper capability verification.

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 2.3.7 or later
Fixed in 2.3.7
Interim mitigation

Upgrade to the latest version of the Aiomatic plugin (currently 2.3.6 according to the description; verify patch status with vendor) and audit all functions for proper current_user_can() capability checks. Restrict the Subscriber role permissions until the patch is verified.

Recommended fix High confidence

2.3.7 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Aiomatic plugin in the list
  4. Verify current version is below 2.3.7
  5. Click Update now or update to the latest available version
  6. Verify the plugin has been updated to version 2.3.7 or higher

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

Fix this in Aiomatic Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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