CVE-2024-10536

FancyPost – Best Ultimate Post Block, Post Grid, Layouts, Carousel, Slider For Gutenberg & Elementor <= 6.0.0 - Missing Authorization to Authenticated (Subscriber+) Shortcode Export

2025-01-06 16:23
Tieu Pham Trong Nhan

Strategic Overview

Status
Patched in 6.0.1
Affected Version
<= 6.0.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-10536
View all FancyPost – Post Blocks, Grids & Sliders for Block Editor and Elementor vulnerabilities

At a glance

CVE-2024-10536 is a medium-severity Missing Authorization vulnerability in the FancyPost WordPress plugin, affecting versions <= 6.0.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.0.1; sites on affected versions should update now. Disclosed January 2025, reported by Tieu Pham Trong Nhan.

Vulnerability Overview

The FancyPost – Best Ultimate Post Block, Post Grid, Layouts, Carousel, Slider For Gutenberg & Elementor plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the handle_block_shortcode_export() function in all versions up to, and including, 6.0.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to export shortcodes.

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

FancyPost <= 6.0.0 carries this weakness at handle_block_shortcode_export(), and reaching it takes an account at Subscriber level or above. 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 FancyPost the fix is 6.0.1: builds <= 6.0.0 are affected, anything from 6.0.1 onward is not.

Remediation

Update to version 6.0.1, 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: FancyPost 6.0.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Other vulnerabilities in FancyPost – Post Blocks, Grids & Sliders for Block Editor and Elementor

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