Dashicons + Custom Post Types <= 1.0.2 - Missing Authorization
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Dashicons + Custom Post Types
- Affected Version
<= 1.0.2- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-22674
At a glance
CVE-2023-22674 is a high-severity Missing Authorization vulnerability in the Dashicons + Custom Post Types WordPress plugin, affecting versions <= 1.0.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability 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 January 2023, reported by István Márton.
Vulnerability Overview
The Dashicons + Custom Post Types plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on an unknown function in versions up to, and including, 1.0.2. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to invoke this function intended for higher-privileged users.
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 confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in Dashicons + Custom Post Types <= 1.0.2 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 Dashicons + Custom Post Types yet, so installs running <= 1.0.2 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