CVE-2024-54311

Mark New Posts <= 7.5.1 - Missing Authorization via save_options

2024-12-11 00:00
Jingle Bells

Strategic Overview

Status
Patched in 7.6
Affected Plugin
Mark New Posts
Affected Version
<= 7.5.1
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-54311
View all Mark New Posts vulnerabilities

At a glance

CVE-2024-54311 is a medium-severity Missing Authorization vulnerability in the Mark New Posts WordPress plugin, affecting versions <= 7.5.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 7.6; sites on affected versions should update now. Disclosed December 2024, reported by Jingle Bells.

Vulnerability Overview

The Mark New Posts plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the save_options() function in versions up to, and including, 7.5.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to change plugin settings.

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 interaction from a victim user.

CWE-862: Missing Authorization

Mark New Posts <= 7.5.1 carries this weakness at save_options(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Mark New Posts the fix is 7.6: builds <= 7.5.1 are affected, anything from 7.6 onward is not.

Remediation

Update to version 7.6, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Mark New Posts 7.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

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