dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-0615

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-02
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
The Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks & More plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.1.0 via the API. This makes it possible for unauthenticated attackers to extract post titles, IDs, slugs, statuses and other information including post content. This includes published content only.

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 Content Control WordPress plugin has an unauthenticated API endpoint that exposes sensitive post metadata (titles, IDs, slugs, statuses) and full post content for all published posts. Attackers can harvest this information without any authentication.

MitigationUpdate the plugin to version 2.1.1 or later to patch the vulnerable API endpoint. If immediate update is not possible, temporarily disable the plugin or use server-level access controls to restrict the affected API route.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Content Control plugin is installed
    Check the WordPress plugins directory for the 'content-control' or 'content-control-wordpress-plugin' folder in wp-content/plugins/, or query the wp_plugins database table for the plugin
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin is found in the wp_plugins table
  2. Check the installed plugin version
    Open the main plugin file (usually content-control.php) and look for the 'Version' header in the plugin comments, or check the wp_options table for the active_plugins option
    Affected if The version is lower than 2.1.1 (the fixed version)
  3. Confirm the plugin is active
    Check the WordPress admin dashboard under Plugins > Installed Plugins, or query the wp_options table for the 'active_plugins' option containing 'content-control'
    Affected if The plugin appears active in the WordPress admin or the active_plugins option contains the plugin
  4. Test for unauthenticated API endpoint access
    Use a tool like curl to send a GET request to common API routes such as /wp-json/content-control/v1/posts or /wp-json/cc/v1/posts without providing any authentication tokens
    Affected if The endpoint returns JSON data containing post metadata or full post content without requiring any authentication (HTTP 200 response with post data)
  5. Inspect network traffic during plugin interaction
    If you have admin access, visit the plugin settings page in WordPress admin and use browser developer tools to observe any API calls made to endpoints under /wp-json/content-control/ or similar
    Affected if API endpoints are reachable without authentication and return sensitive post information

A user is affected if the Content Control plugin version is below 2.1.1 AND the unauthenticated API endpoint is accessible and returns post data without login.

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 the plugin to version 2.1.1 or later to patch the vulnerable API endpoint. If immediate update is not possible, temporarily disable the plugin or use server-level access controls to restrict the affected API route.

Recommended fix Moderate confidence

Latest version of Content Control plugin (verify version > 2.1.0)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Content Control – The Ultimate Content Restriction Plugin!'
  4. Check if an update is available and update to the latest version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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