Smart Post – Post Grid, Post Carousel, Post Slider Gutenberg Blocks for Blog & News 4.0.0 - 4.0.7 - Authenticated (Contributor+) Insecure Direct Object Reference
Strategic Overview
- Status
- Patched in 4.0.8
- Affected Version
4.0.0 – 4.0.7- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-78150
At a glance
CVE-2026-78150 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Smart Post WordPress plugin, affecting versions 4.0.0 – 4.0.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.0.8; sites on affected versions should update now. Disclosed September 2026, reported by Revanth Hari Narayana Matte.
Vulnerability Overview
The Smart Post – Post Grid, Post Carousel, Post Slider Gutenberg Blocks for Blog & News plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions 4.0.0 through 4.0.7. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.
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-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Smart Post 4.0.0 – 4.0.7 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Smart Post the fix is 4.0.8: builds 4.0.0 – 4.0.7 are affected, anything from 4.0.8 onward is not.
Remediation
Update to version 4.0.8, 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: Smart Post 4.0.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Smart Post – Post Grid, Post Carousel, Post Slider Gutenberg Blocks for Blog & News
- 7.3Post Carousel < 2.3.5 Missing Capabilities Check
- 7.2CVE-2026-3017: Smart Post Show PHP Object Injection
CVE-2026-3017 - 6.4CVE-2023-0097: Post Grid Stored XSS
CVE-2023-0097 - 5.5CVE-2024-8187: Smart Post Show <= 3.0.0 Stored Cross-Site Scripting
CVE-2024-8187 - 5.3CVE-2026-78149: Smart Post Password-Protected Post Content Disclosure
CVE-2026-78149 - 4.4CVE-2024-3996: Post Grid Stored XSS
CVE-2024-3996
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C