dbcve.org
Shariff WrapperWordPress extension · Datenverwurstungszentrale

CVE-2024-29109

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 4.6.11 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Jan-Peter Lambeck & 3UU Shariff Wrapper allows Stored XSS.This issue affects Shariff Wrapper: from n/a through 4.6.10.

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 · moderate confidence

Stored XSS vulnerability in the Shariff Wrapper WordPress plugin allows authenticated or unauthenticated attackers to inject malicious JavaScript through unsanitized user input that gets stored on the server and executed in the browsers of users who view affected pages.

MitigationUpdate Shariff Wrapper to version 4.6.11 or later which contains proper input sanitization; alternatively, implement output escaping for all user-supplied data before rendering in HTML contexts.

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
Shariff WrapperWordPress extension
Affected:< 4.6.11

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. Check if Shariff Wrapper plugin is installed
    Navigate to Plugins > Installed Plugins in WordPress admin, or inspect the /wp-content/plugins/ directory for the shariff-wrapper folder
    Affected if The plugin folder 'shariff-wrapper' exists in the WordPress plugins directory
  2. Identify the installed version number
    In WordPress admin, find Shariff Wrapper in the Plugins list and read the version number under the plugin name; alternatively, check the main plugin PHP file for the 'Version' header comment
    Affected if The displayed version is lower than 4.6.11 (e.g., 4.6.10, 4.6.0, or any version below 4.6.11)
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm that Shariff Wrapper shows as 'Active' rather than 'Inactive'
    Affected if The plugin status is Active and the version is below 4.6.11
  4. Inspect for stored malicious scripts in the database
    Query the WordPress database (wp_options table or any custom tables created by the plugin) for stored user-supplied values containing script tags, iframe tags, or javascript: URIs; use: SELECT * FROM wp_options WHERE option_value LIKE '%<script%' OR option_value LIKE '%javascript:%'
    Affected if Any database entries contain unsanitized script tags or event handlers (onclick, onerror, etc.) that could execute JavaScript when viewed

You are affected if the Shariff Wrapper plugin is installed, active, and running a version lower than 4.6.11, or if suspicious script tags are found stored in the database related to this plugin.

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

Update Shariff Wrapper to version 4.6.11 or later which contains proper input sanitization; alternatively, implement output escaping for all user-supplied data before rendering in HTML contexts.

Recommended fix High confidence

4.6.11

  1. Update Shariff Wrapper plugin to version 4.6.11 via WordPress plugin dashboard, or download from the WordPress plugin repository
  2. After updating, verify the plugin is running version 4.6.11 in the plugins list
  3. Test that the Shariff sharing buttons function correctly on the frontend

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

Fix this in Shariff Wrapper 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-2024-29109 — 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-29109 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