dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1984

MEDIUM · 5.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 →
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 Graphene theme for WordPress is vulnerable to unauthorized access of data via meta tag in all versions up to, and including, 2.9.2. This makes it possible for unauthenticated individuals to obtain post contents of password protected posts via the generated source.

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

The Graphene WordPress theme versions up to 2.9.2 improperly exposes password-protected post content through meta tags in the HTML source. Unauthenticated attackers can view the protected content by inspecting the page source, bypassing WordPress's password protection mechanism.

MitigationUpdate the Graphene theme to version 2.9.3 or later. If no update is available, consider replacing the theme or removing meta tag generation logic that outputs post content for password-protected posts.

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. Confirm Graphene theme is installed
    In WordPress admin, go to Appearance > Themes and verify the Graphene theme is active
    Affected if Graphene theme is the active theme
  2. Check Graphene theme version
    Inspect the theme's style.css file (typically in wp-content/themes/graphene/) and locate the Version: header in the theme comment block
    Affected if Version is 2.9.2 or lower
  3. Identify password-protected posts
    In WordPress admin, go to Posts > All Posts and look for posts with a padlock icon indicating password protection, or query the wp_posts table where post_password is not empty
    Affected if Any password-protected posts exist on the site
  4. Inspect HTML source for exposed content
    Visit a password-protected post as an unauthenticated user, view the page source (Ctrl+U or Cmd+U), and search for meta tags or hidden input fields containing the actual post title, excerpt, or content
    Affected if Protected post content appears in HTML meta tags or hidden fields without requiring the password

If Graphene theme version 2.9.2 or lower is active and password-protected posts exist with content visible in the HTML source, the site is affected by this vulnerability.

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 Graphene theme to version 2.9.3 or later. If no update is available, consider replacing the theme or removing meta tag generation logic that outputs post content for password-protected posts.

Recommended fix High confidence

Graphene theme version 2.9.3 or latest available version

  1. Navigate to the WordPress admin dashboard
  2. Go to Appearance > Themes
  3. Locate the Graphene theme
  4. If an update is available, click 'Update Now' to upgrade to the latest version (2.9.3 or later)
  5. Alternatively, download the latest Graphene theme from the WordPress theme repository and upload it via Appearance > Themes > Add New > Upload Theme

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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