Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Craw Data
- Affected Version
<= 1.0.0- CVSS
- 7.4High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2022-2912
At a glance
CVE-2022-2912 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Craw Data WordPress plugin, affecting versions <= 1.0.0. It carries a CVSS score of 7.4 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2022, reported by Dhanesh Sivasamy.
Vulnerability Overview
The Craw Data plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 1.0.0 due to missing nonce checks, which could allow attackers to make a logged in admin change the URL value resulting in unwanted crawls on third-party sites.
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.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Craw Data <= 1.0.0 takes a caller who can reach the endpoint. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. No fixed build of this plugin is recorded for Craw Data yet, so installs running <= 1.0.0 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?
The attempt arrives as an ordinary request to Craw Data: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C