dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-30459

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 AIpost AI WP Writer.This issue affects AI WP Writer: from n/a through 3.6.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 · moderate confidence

This is a Missing Authorization vulnerability in the AIpost AI WP Writer WordPress plugin (versions through 3.6.5). Missing authorization vulnerabilities allow unauthenticated or low-privilege users to access functionality that should be restricted to authenticated administrators or higher-privileged users. The CVSS 5.3 indicates the attack can be exploited with low complexity and no privileges required.

MitigationApply the vendor patch (upgrade to version 3.6.6 or later) which adds proper authorization checks. If no patch is available, restrict access to the plugin's admin functions via server-side configuration or disable the plugin until a fix is released.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify AIpost AI WP Writer plugin is installed
    Access WordPress admin > Plugins page, or inspect the /wp-content/plugins/ directory for aipost-ai-wp-writer folder via file manager or FTP
    Affected if Plugin folder does not exist - not affected
  2. Determine installed plugin version
    On WordPress Plugins page, read the version number listed under the AIpost AI WP Writer plugin, or open the main plugin PHP file and check the Version header comment
    Affected if Version cannot be determined or is 3.6.5 or lower - may be affected
  3. Confirm plugin is active
    Check WordPress admin > Plugins > Active Plugins list, or inspect wp_options table for active_plugins entry containing aipost-ai-wp-writer
    Affected if Plugin is active and version is 3.6.5 or lower - environment is vulnerable to unauthorized access

The environment is affected if AIpost AI WP Writer plugin is installed, active, and running version 3.6.5 or earlier.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (upgrade to version 3.6.6 or later) which adds proper authorization checks. If no patch is available, restrict access to the plugin's admin functions via server-side configuration or disable the plugin until a fix is released.

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-30459 — 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-30459 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