LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2912: Craw Data <= 1.0.0 - Server Side Request Forgery

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).

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects the Craw Data WordPress plugin through version 1.0.0. An attacker may trick a logged-in administrator into changing the plugin’s URL setting, causing unwanted crawls against third-party sites. Business impact is likely limited, but affected sites should treat it as a plugin governance and outbound-request control issue.

Executive priority

Handle during normal vulnerability remediation unless the plugin is widely deployed or outbound requests are sensitive. Prioritize removal or vendor-confirmed update because no patch details are provided in the source bundle.

Technical view

The plugin lacks nonce checks around changing the URL value, creating a CSRF-style path to trigger SSRF behavior through an authenticated administrator’s session. CVSS 3.1 is 4.3 with required user interaction and low integrity impact. The sources do not identify a fixed version or confirmed exploit activity.

Likely exposure

Exposure is limited to WordPress sites running Craw Data version 1.0.0 or earlier, especially where administrators can be targeted with links or pages while logged in. The source bundle names no other affected products or CPEs.

Exploitation context

The bundle does not show KEV listing or confirmed active exploitation. Abuse appears to require social engineering or web content that causes a logged-in admin to submit an unintended plugin setting change.

Researcher notes

Evidence supports a missing nonce check leading to attacker-influenced URL changes and SSRF-like unwanted crawls. Public details are sparse: no exploit proof, fixed version, vendor identity, or patch commit is included. Avoid assuming broader WordPress core exposure.

Mitigation direction

  • Inventory WordPress sites for Craw Data version 1.0.0 or earlier.
  • Check WPScan and vendor guidance for any fixed release or official workaround.
  • Disable or remove the plugin if it is not operationally required.
  • Restrict WordPress administrator access and reduce persistent admin sessions.
  • Review outbound egress controls for unexpected crawl destinations.

Validation and detection

  • Confirm whether Craw Data is installed on each WordPress instance.
  • Record installed plugin versions and flag version 1.0.0 or earlier.
  • Review plugin settings for unexpected URL values.
  • Check web and egress logs for unusual crawl targets.
  • Verify administrators understand not to browse untrusted links while logged in.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-2912 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-2912Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownCraw Data1.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.