dbcve.org
Share This ImageWordPress extension · Share This Image Project

CVE-2024-8108

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-31
Fix available
A fix is available. Upgrade to 2.02 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Share This Image plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'alignment' parameter in all versions up to, and including, 2.01 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Share This Image WordPress plugin (versions up to 2.01) fails to sanitize the 'alignment' parameter input and escape it during output, allowing authenticated users with Contributor-level access to inject malicious JavaScript that persists and executes for all visitors of affected pages.

MitigationUpdate the plugin to a version beyond 2.01 that includes proper input sanitization (sanitize_text_field or similar) and output escaping (esc_attr, esc_html) for the alignment parameter.

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
Share This ImageWordPress extension
Affected:< 2.02

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Share This Image plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'share-this-image' or similar, and read the main plugin file header to find the declared Version.
    Affected if The plugin folder exists and the version declared in the plugin header is less than 2.02 (e.g., 2.01, 2.0, 1.x).
  2. Check plugin version in WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard and locate 'Share This Image' in the list to view the installed version number.
    Affected if The version displayed is anything less than 2.02.
  3. Identify posts using the alignment feature
    Query the wp_postmeta table for meta_key values containing 'alignment' or 'sti_alignment' (the exact key depends on the plugin's implementation), or inspect page content where the Share This Image shortcode or block is used.
    Affected if Any posts or pages contain the alignment parameter stored in the database, indicating the feature is in use.
  4. Inspect the vulnerable parameter handling in plugin code
    Examine the plugin's PHP files for the code handling the 'alignment' parameter - look for instances where $_POST, $_GET, or request variables are used without sanitize_text_field or similar sanitization, and where the alignment value is output without esc_attr or esc_html.
    Affected if The code shows the alignment parameter is output without proper escaping (no esc_attr, esc_html, or sanitize_text_field on input).

You are affected if the Share This Image plugin is installed with a version below 2.02 AND the alignment parameter is used on any published content, as the stored XSS will execute for all visitors viewing those pages.

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

Update the plugin to a version beyond 2.01 that includes proper input sanitization (sanitize_text_field or similar) and output escaping (esc_attr, esc_html) for the alignment parameter.

Recommended fix High confidence

2.02

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Share This Image' in the plugin list
  4. Check if the current version is below 2.02
  5. If update available, click 'Update Now' to upgrade to version 2.02
  6. If no automatic update is available, manually upload version 2.02 of the plugin from the WordPress plugin repository
  7. Verify the plugin is now running version 2.02

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

Fix this in Share This Image Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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