CVE-2024-12294

Last Viewed Posts by WPBeginner <= 1.0.1 - Unauthenticated Sensitive Information Exposure

2024-12-10 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 1.0.2
Affected Version
<= 1.0.1
CVSS
5.3Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2024-12294
View all Last Viewed Posts by WPBeginner vulnerabilities

At a glance

CVE-2024-12294 is a medium-severity Improper Access Control vulnerability in the Last Viewed Posts by WPBeginner WordPress plugin, affecting versions <= 1.0.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.2; sites on affected versions should update now. Disclosed December 2024, reported by Francesco Carlucci.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-284: Improper Access Control

Last Viewed Posts by WPBeginner <= 1.0.1 carries this weakness at get_legacy_cookies, and reaching it takes no account at all. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For Last Viewed Posts by WPBeginner the fix is 1.0.2: builds <= 1.0.1 are affected, anything from 1.0.2 onward is not.

Remediation

Update to version 1.0.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Last Viewed Posts by WPBeginner 1.0.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Other vulnerabilities in Last Viewed Posts by WPBeginner

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C