dbcve.org
GetwidWordPress extension · Motopress

CVE-2023-1895

CRITICAL · 9.6 CVSS v3.1 Published 2023-06-09
Fix available
A fix is available. Upgrade to after 1.8.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Getwid – Gutenberg Blocks plugin for WordPress is vulnerable to Server Side Request Forgery via the get_remote_content REST API endpoint in versions up to, and including, 1.8.3. This can allow authenticated attackers with subscriber-level permissions or above to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Getwid WordPress plugin contains an SSRF vulnerability in its get_remote_content REST API endpoint (versions up to 1.8.3). Authenticated users with subscriber-level permissions can abuse this endpoint to make arbitrary HTTP requests from the server, potentially reaching internal services, cloud metadata endpoints, or internal network resources.

MitigationUpdate the Getwid plugin to version 1.8.4 or later, which contains the SSRF fix. If unable to update immediately, disable or restrict access to the get_remote_content REST API endpoint via WordPress hooks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GetwidWordPress extension
Affected:<= 1.8.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Getwid plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Motopress Getwid' in the list. Alternatively, check the file /wp-content/plugins/getwid/ for existence.
    Affected if Getwid plugin is present in the WordPress installation
  2. Check installed Getwid version
    In WordPress admin, go to Plugins > Installed Plugins and locate the Getwid plugin to view its version number. Alternatively, check /wp-content/plugins/getwid/readme.txt for the 'Stable tag' entry.
    Affected if Version is 1.8.3 or lower (any version up to and including 1.8.3)
  3. Confirm REST API endpoint is accessible
    Send a GET request to /wp-json/getwid/v1/remote_content to verify the endpoint exists and responds. Use an authenticated request with a subscriber-level user account.
    Affected if Endpoint responds with valid JSON (indicating the vulnerable endpoint is active)
  4. Verify subscriber-level accounts exist
    In WordPress admin, go to Users and review user roles. Check if any users have the 'Subscriber' role assigned.
    Affected if Any subscriber-level or higher authenticated user accounts exist in the system

The environment is affected if Getwid plugin version 1.8.3 or lower is installed and the get_remote_content REST API endpoint is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.8.3
Interim mitigation

Update the Getwid plugin to version 1.8.4 or later, which contains the SSRF fix. If unable to update immediately, disable or restrict access to the get_remote_content REST API endpoint via WordPress hooks.

Recommended fix Moderate confidence

Getwid 1.8.4

  1. 1. Back up your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Getwid plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download Getwid version 1.8.4 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the get_remote_content REST API endpoint is no longer accessible to subscriber-level users

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Getwid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1895 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data