DX Share Selection <= 1.4 - Cross-Site Request Forgery to Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.5
- Affected Plugin
- DX Share Selection
- Affected Version
<= 1.4- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-2001
At a glance
CVE-2022-2001 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the DX Share Selection WordPress plugin, affecting versions <= 1.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.5; sites on affected versions should update now. Disclosed June 2022, reported by Sho Sakata.
Vulnerability Overview
The DX Share Selection plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including 1.4. This is due to missing nonce protection on the dxss_admin_page() function found in the ~/dx-share-selection.php file. This makes it possible for unauthenticated attackers to inject malicious web scripts into the page, granted they 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
DX Share Selection <= 1.4 carries this weakness at dxss_admin_page(), and reaching it 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 DX Share Selection the fix is 1.5: builds <= 1.4 are affected, anything from 1.5 onward is not.
Remediation
Update to version 1.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to DX Share Selection: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: DX Share Selection 1.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C