CVE-2023-30488

Featured Post Creative <= 1.2.7 - Cross-Site Request Forgery via wpfp_update_featured_post

2023-04-13 00:00
Anonymous

Strategic Overview

Status
Patched in 1.2.8
Affected Plugin
Featured Post Creative
Affected Version
<= 1.2.7
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-30488
View all Featured Post Creative vulnerabilities

At a glance

CVE-2023-30488 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Featured Post Creative WordPress plugin, affecting versions <= 1.2.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.8; sites on affected versions should update now. Disclosed April 2023.

Vulnerability Overview

The Featured Post Creative plugin for WordPress is vulnerable to Cross-Site Request Forgery due to missing nonce verification on the wpfp_update_featured_post function called via an AJAX action in versions up to, and including, 1.2.7. This makes it possible for unauthenticated attackers to change what post is featured via forged request, granted the attacker can trick a site's administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Featured Post Creative <= 1.2.7 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Featured Post Creative the fix is 1.2.8: builds <= 1.2.7 are affected, anything from 1.2.8 onward is not.

Remediation

Update to version 1.2.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Featured Post Creative: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Featured Post Creative 1.2.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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