dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-30488

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
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 WP OnlineSupport, Essential Plugin Featured Post Creative allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Featured Post Creative: from n/a through 1.2.7.

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 Featured Post Creative WordPress plugin allows attackers to access functionality that should require proper authentication and authorization. The plugin fails to enforce adequate access control checks, potentially enabling unauthorized users to perform actions intended for privileged users.

MitigationUpdate Featured Post Creative to the latest version to obtain the security patch that adds proper authorization checks. If no update is available, consider disabling the plugin until a patched version 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. Locate the Featured Post Creative plugin files
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'featured-post-creative' or similar variant. List all directories in the plugins folder and search for the plugin name.
    Affected if The plugin directory exists in the WordPress installation
  2. Verify the plugin is active
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and confirm Featured Post Creative is activated. Alternatively, check the wp_options table for the active_plugins option.
    Affected if The plugin shows as activated in WordPress admin or appears in the active_plugins database option
  3. Determine the installed plugin version
    Open the main plugin PHP file (usually featured-post-creative.php or similar in the plugin folder) and locate the version string in the plugin header comment (e.g., 'Version: 1.2.3').
    Affected if The version displayed is older than the patched version that added proper authorization checks
  4. Inspect plugin endpoints for access control
    Review the plugin PHP files for AJAX handlers, admin pages, or public endpoints. Search for 'add_action' calls registering hooks and check if they include capability checks (e.g., 'current_user_can' or 'wp_verify_nonce').
    Affected if The plugin registers action hooks without verifying user capabilities or nonces before executing privileged operations
  5. Check for unauthorized access vectors
    If possible, attempt to access plugin functionality while logged out or with a low-privilege user account. Look for admin actions, settings modifications, or post management functions that should require authentication.
    Affected if The plugin permits actions to execute without proper user authentication or authorization validation

A WordPress site is affected if the Featured Post Creative plugin is installed and active, and the installed version lacks the authorization patch that enforces proper access control checks.

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 Featured Post Creative to the latest version to obtain the security patch that adds proper authorization checks. If no update is available, consider disabling the plugin until a patched version is released.

Recommended fix Moderate confidence

Update Featured Post Creative plugin to version 1.3.0 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Featured Post Creative' plugin
  4. If update available, click 'Update Now' to install the latest version
  5. Alternatively, deactivate the vulnerable plugin and install the latest version from WordPress.org repository
  6. Verify the plugin is updated to version 1.3.0 or later

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-2023-30488 — 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-2023-30488 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