dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-12294

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-11
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 Last Viewed Posts by WPBeginner plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.1 via the 'get_legacy_cookies' function. This makes it possible for unauthenticated attackers to extract sensitive data including titles and permalinks of private, password-protected, pending, and draft posts.

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 Last Viewed Posts WordPress plugin versions up to 1.0.1 expose sensitive post data via the get_legacy_cookies function, allowing unauthenticated attackers to retrieve titles and permalinks of private, password-protected, pending, and draft posts that should not be accessible to public users.

MitigationUpdate the plugin to version 1.0.2 or later, which contains the fix for this vulnerability. If immediate updating is not possible, disable the plugin until the update can be applied.

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 the Last Viewed Posts plugin is installed
    Check the WordPress plugins directory for the 'last-viewed-posts' folder or navigate to wp-admin > Plugins and locate the Last Viewed Posts plugin
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    Navigate to wp-admin > Plugins > Last Viewed Posts and view the version number displayed, or read the main plugin file (usually last-viewed-posts.php) and locate the Version header in the plugin comment block
    Affected if The version is 1.0.1 or earlier (any version up to and including 1.0.1)
  3. Identify if private or sensitive posts exist
    Log in to wp-admin and review the Posts list to see if any posts are set to Private, Password Protected, Pending, or Draft status
    Affected if Any such posts exist in the WordPress database
  4. Test for unauthenticated data exposure
    Send a direct HTTP request to the site and inspect whether the get_legacy_cookies function or related endpoints return post titles or permalinks that should be restricted (private, draft, pending, or password-protected posts) without authentication
    Affected if The response contains titles or permalinks of non-public posts without requiring authentication

You are affected if the Last Viewed Posts plugin version is 1.0.1 or earlier AND your site contains private, password-protected, pending, or draft posts that could be exposed to unauthenticated users through the vulnerable function.

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 1.0.2 or later, which contains the fix for this vulnerability. If immediate updating is not possible, disable the plugin until the update can be applied.

Recommended fix High confidence

Update to latest version (version higher than 1.0.1)

  1. Check the current version of the 'Last Viewed Posts by WPBeginner' plugin installed on your WordPress site
  2. Navigate to Plugins > Instored Plugins in the WordPress admin dashboard
  3. Locate 'Last Viewed Posts by WPBeginner' and note the current version
  4. If the installed version is 1.0.1 or below, update the plugin to the latest available version
  5. Verify the update completed successfully and the new version is active
  6. Test that the plugin functionality still works as expected

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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