Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2022-2912: CWE-918 Server-Side Request Forgery (SSRF) in Unknown Craw Data

0
Medium
VulnerabilityCVE-2022-2912cvecve-2022-2912cwe-918
Published: Fri Sep 16 2022 (09/16/2022, 08:40:38 UTC)
Source: CVE Database V5
Vendor/Project: Unknown
Product: Craw Data

Description

The Craw Data WordPress plugin through 1.0.0 does not implement nonce checks, which could allow attackers to make a logged in admin change the url value performing unwanted crawls on third-party sites (SSRF).

AI-Powered Analysis

AILast updated: 07/04/2025, 09:28:10 UTC

Technical Analysis

CVE-2022-2912 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Craw Data WordPress plugin version 1.0.0 and earlier. The vulnerability arises because the plugin does not implement nonce checks, a security mechanism used in WordPress to verify that requests originate from legitimate sources. This lack of nonce validation allows an attacker who can induce a logged-in administrator to perform an action (requiring user interaction) to manipulate the 'url' parameter used by the plugin to perform crawling operations. By changing this URL value, the attacker can cause the server to make HTTP requests to arbitrary third-party sites, effectively enabling SSRF attacks. SSRF vulnerabilities can be leveraged to access internal resources, bypass firewalls, or perform reconnaissance on internal networks. However, exploitation requires that the attacker convince an authenticated admin user to perform the action, as no privilege escalation or unauthenticated exploitation is possible. The CVSS v3.1 base score is 4.3 (medium severity), reflecting the need for user interaction and the limited impact on confidentiality and availability. The vulnerability affects only version 1.0.0 of the Craw Data plugin, which is not a widely known or broadly used WordPress plugin, and no known exploits have been reported in the wild to date.

Potential Impact

For European organizations using WordPress sites with the Craw Data plugin version 1.0.0, this vulnerability could allow attackers to induce administrators to trigger unwanted crawling requests to arbitrary URLs. While the direct impact on confidentiality and availability is limited, SSRF can be a stepping stone for more complex attacks, such as accessing internal services not exposed externally or performing internal network reconnaissance. This could be particularly concerning for organizations with sensitive internal web services or intranet applications. However, since exploitation requires an authenticated admin user and user interaction, the risk is somewhat mitigated by standard administrative access controls. The medium CVSS score reflects this limited but non-negligible risk. Organizations in sectors with high-value internal resources, such as finance, healthcare, or government, should be especially cautious. Additionally, the lack of nonce checks indicates a general weakness in the plugin's security design, which could lead to other vulnerabilities if not addressed.

Mitigation Recommendations

Specific mitigation steps include: 1) Immediately update or remove the Craw Data plugin if it is version 1.0.0 or earlier, as no patch links are currently available, and consider replacing it with a more secure alternative. 2) If updating is not possible, restrict administrative access to trusted personnel only and enforce strong authentication mechanisms such as multi-factor authentication to reduce the risk of an attacker leveraging an admin session. 3) Educate administrators about phishing and social engineering risks to prevent attackers from tricking them into performing malicious actions. 4) Implement network-level controls such as egress filtering to restrict the server's ability to make arbitrary outbound HTTP requests, limiting the impact of SSRF exploitation. 5) Monitor logs for unusual outbound requests originating from the WordPress server that could indicate exploitation attempts. 6) Conduct regular security audits of WordPress plugins to ensure they follow best practices, including nonce verification for state-changing operations.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
WPScan
Date Reserved
2022-08-19T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 683f3437182aa0cae2861730

Added to database: 6/3/2025, 5:43:19 PM

Last enriched: 7/4/2025, 9:28:10 AM

Last updated: 2/7/2026, 8:21:47 AM

Views: 43

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats