dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1850

MEDIUM · 6.3 CVSS v3.1 Published 2024-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 AI Post Generator | AutoWriter plugin for WordPress is vulnerable to unauthorized access, modification or deletion of posts due to a missing capability check on functions hooked by AJAX actions in all versions up to, and including, 3.3. This makes it possible for authenticated attackers, with subscriber access or higher, to view all posts generated with this plugin (even in non-published status), create new posts (and publish them), publish unpublished post or perform post deletions. CVE-2024-32713 may be a duplicate of this issue.

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 AI Post Generator | AutoWriter WordPress plugin lacks capability checks on AJAX action handlers, allowing any authenticated user with subscriber-level access or higher to view all posts (including unpublished drafts), create new posts, publish existing unpublished posts, and delete posts without proper authorization.

MitigationUpdate to the latest patched version when available. Until then, restrict user registration or remove the plugin if not essential, and audit user accounts for unauthorized content.

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

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

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 plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'AI Post Generator | AutoWriter' or check the plugin files in /wp-content/plugins/ for the plugin directory
    Affected if The plugin is installed and active
  2. Check plugin version
    In WordPress admin Plugins page, click on the plugin to view details and note the version number. Compare against any official vulnerability disclosure
    Affected if Version is earlier than the patched version (if known) or remains unpatched
  3. Audit user accounts with subscriber-level access
    Go to Users > All Users in WordPress admin. Review each user role - look for any accounts with Subscriber, Contributor, Author, or Editor roles that you did not create or that appear unauthorized
    Affected if There are any user accounts with subscriber-level or higher access that were not explicitly authorized
  4. Inspect for unauthorized post activity
    Go to Posts > All Posts in WordPress admin. Look for drafts, published posts, or modifications that were not created by administrators. Check post author IDs against expected admin user IDs
    Affected if There are posts created by non-admin users or posts in states (published/drafted) that you did not create
  5. Test AJAX endpoint accessibility (if feasible)
    If you have access to site debugging, verify that AJAX actions for this plugin (typically wp-admin/admin-ajax.php?action=ai_post_generator_*) respond to requests from low-privilege users without capability validation
    Affected if AJAX endpoints accept and process requests from authenticated users with subscriber-level roles without proper authorization checks

Your environment is affected if the AI Post Generator | AutoWriter plugin is installed and you have any user accounts with subscriber-level or higher access, regardless of whether you have observed exploitation yet.

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 the latest patched version when available. Until then, restrict user registration or remove the plugin if not essential, and audit user accounts for unauthorized content.

Recommended fix Moderate confidence

latest version available on WordPress plugin repository (newer than 3.3)

  1. Identify the currently installed version of the AI Post Generator | AutoWriter plugin in WordPress
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the AI Post Generator | AutoWriter plugin
  4. Check if the installed version is 3.3 or below
  5. If vulnerable, update the plugin to the latest available version from the WordPress plugin repository
  6. Verify the update was successful and the new version does not have this vulnerability

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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