dbcve.org
Shoppable ImagesWordPress extension · Studiowombat

CVE-2023-25698

HIGH · 8.8 CVSS v3.1 Published 2023-05-18
Fix available
A fix is available. Upgrade to 1.2.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Studio Wombat Shoppable Images plugin <= 1.2.3 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Studio Wombat Shoppable Images WordPress plugin versions 1.2.3 and below allows attackers to trick authenticated users into performing unintended actions by crafting malicious requests, potentially leading to unauthorized configuration changes or data manipulation.

MitigationUpdate the Studio Wombat Shoppable Images plugin to the latest version which should include proper nonce validation and CSRF token verification for all state-changing requests.

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
Shoppable ImagesWordPress extension
Affected:< 1.2.4

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate the Studio Wombat plugin files
    Navigate to wp-content/plugins/ in your WordPress installation directory and search for a folder named 'shoppable-images' or 'studiowombat'. Alternatively, go to WordPress Admin > Plugins and look for 'Studio Wombat Shoppable Images' in the plugin list.
    Affected if The plugin folder or listing is found in your WordPress installation.
  2. Identify the installed version number
    In WordPress Admin, go to Plugins > Installed Plugins and click on the plugin name 'Studio Wombat Shoppable Images' to view its details, which typically display the version number. Alternatively, open the main plugin PHP file (usually shoppable-images.php or similar) in the plugin folder and look for a version comment or constant at the top of the file.
    Affected if The version displayed is 1.2.3 or lower.
  3. Verify WordPress user authentication state
    Check if any administrative or editor-level user accounts exist and have active sessions. CSRF attacks require an authenticated user to be logged in when they click a malicious link. You can review active users under Users > All Users in the WordPress admin panel.
    Affected if Authenticated users with privileged access (administrator, editor, or author) exist on the site.
  4. Confirm plugin state-changing functionality exists
    Access the plugin settings page (usually under Settings > Shoppable Images or a dedicated Studio Wombat menu item) and identify any configuration forms, image management features, or settings that modify plugin data. These represent the endpoints that could be targeted by CSRF.
    Affected if The plugin exposes any configuration or data modification forms to authenticated users.

You are affected if the Studio Wombat Shoppable Images plugin is installed and active with version 1.2.3 or below, and any authenticated users with permission to modify plugin settings exist on the site.

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 1.2.4 or later
Fixed in 1.2.4
Interim mitigation

Update the Studio Wombat Shoppable Images plugin to the latest version which should include proper nonce validation and CSRF token verification for all state-changing requests.

Recommended fix High confidence

1.2.4

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Shoppable Images plugin by Studio Wombat
  4. Check the current version number to confirm it is 1.2.3 or below
  5. If an update is available, click 'Update Now' to upgrade to version 1.2.4
  6. Alternatively, navigate to Dashboard > Updates and select the Shoppable Images plugin to update
  7. Verify the update was successful by confirming the plugin now shows version 1.2.4

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

Fix this in Shoppable Images Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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