dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2022-1751

HIGH · 7.2 CVSS v3.1 Published 2024-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 Skitter Slideshow plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.5.2 via the /image.php file. This makes it possible for unauthenticated attackers 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 Skitter Slideshow plugin for WordPress contains an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the /image.php file affecting all versions up to and including 2.5.2. Attackers can abuse this to make arbitrary web requests from the server, potentially accessing internal services, querying databases, or pivoting to internal network resources.

MitigationUpdate the Skitter Slideshow plugin to the latest version beyond 2.5.2, or if no patched version exists, remove the plugin entirely. Consider implementing network-level controls to restrict outgoing connections from the web server as an additional defense-in-depth measure.

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

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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 Skitter Slideshow plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'skitter-slideshow' or 'skitter', or query the WordPress database wp_options table for the plugin entry.
    Affected if The plugin folder exists in the plugins directory or is registered in WordPress.
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically skitter-slideshow.php or similar in the plugin folder) and locate the Version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' value.
    Affected if The version displayed is 2.5.2 or lower.
  3. Confirm the vulnerable image.php file exists
    Locate the /image.php file within the Skitter Slideshow plugin directory (e.g., wp-content/plugins/skitter-slideshow/image.php) and verify it is present on the filesystem.
    Affected if The image.php file exists in the plugin directory.
  4. Check if the plugin is active
    In WordPress admin, navigate to Plugins > Installed Plugins and verify if Skitter Slideshow is activated, or query the wp_options table for the active_plugins option.
    Affected if The plugin shows as 'Active' in WordPress.

You are affected if the Skitter Slideshow plugin is installed, active, version 2.5.2 or lower, and the image.php file is present in the plugin directory.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Skitter Slideshow plugin to the latest version beyond 2.5.2, or if no patched version exists, remove the plugin entirely. Consider implementing network-level controls to restrict outgoing connections from the web server as an additional defense-in-depth measure.

Recommended fix Moderate confidence

Version above 2.5.2 (check WordPress plugin repository for latest release)

  1. 1. Check the current version of the Skitter Slideshow plugin installed on your WordPress site
  2. 2. If the installed version is 2.5.2 or lower, navigate to Plugins > Add New > Upload Plugin in the WordPress admin dashboard
  3. 3. Download the latest version of the Skitter Slideshow plugin from the official WordPress plugin repository
  4. 4. Upload and install the latest version, which should be above 2.5.2
  5. 5. After upgrading, verify the plugin is functioning correctly
  6. 6. Alternatively, you can update directly from the WordPress admin by going to Dashboard > Updates and installing any available updates for the Skitter Slideshow plugin
Caveat Review plugin settings after upgrade as configuration may need adjustment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1751 — 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-2022-1751 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