CVE-2022-40975

Post Slider <= 1.6.7 - Missing Authorization

2022-10-06 00:00
ptsfence

Strategic Overview

Status
Unpatched
Affected Plugin
Post Slider
Affected Version
<= 1.6.7
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2022-40975
View all Post Slider vulnerabilities

At a glance

CVE-2022-40975 is a medium-severity Missing Authorization vulnerability in the Post Slider WordPress plugin, affecting versions <= 1.6.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2022, reported by ptsfence.

Vulnerability Overview

The Post Slider plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the toggle_featured_post() function in versions up to, and including, 1.6.7. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to change featured 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 interaction from a victim user. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

Post Slider <= 1.6.7 carries this weakness at toggle_featured_post(), 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. No fixed build of this plugin is recorded for Post Slider yet, so installs running <= 1.6.7 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

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