dbcve.org
WishsuiteWordPress extension · Hasthemes

CVE-2024-29927

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to 1.3.8 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 HasTheme WishSuite allows Stored XSS.This issue affects WishSuite: from n/a through 1.3.7.

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 Cross-site Scripting (XSS) vulnerability in the HasTheme WishSuite WordPress plugin allows authenticated attackers to inject malicious JavaScript into web pages through improper input neutralization. The stored payload executes when users view affected pages, potentially enabling session hijacking or defacement.

MitigationUpdate WishSuite to the latest patched version. Until patched, implement input validation and output encoding on user-supplied data, and consider deploying a WAF rule to block XSS payloads.

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
WishsuiteWordPress extension
Affected:< 1.3.8

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 WishSuite plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WishSuite' or 'Hasthemes Wishsuite' in the list of installed plugins.
    Affected if WishSuite plugin is present in the plugins directory regardless of active status
  2. Check installed WishSuite version
    In the Plugins list, find WishSuite and note the version number displayed under the plugin name. Compare this version against the vulnerable range: versions prior to 1.3.8 are affected.
    Affected if Installed version is lower than 1.3.8 (for example, 1.3.7, 1.3.6, 1.0.0, etc.)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the WishSuite plugin shows as 'Active'. The vulnerability requires an authenticated attacker, so an active plugin is necessary for exploitation.
    Affected if Plugin is active and running on the site
  4. Identify plugin database tables
    Access the WordPress database (via phpMyAdmin or command line) and locate tables prefixed with 'wishsuite_' or similar. Common tables include wishsuite_wishlist, wishsuite_items, or settings tables.
    Affected if WishSuite database tables exist and contain user-submitted data
  5. Inspect stored data for malicious scripts
    Query the plugin's database tables for content containing HTML script tags, javascript: URIs, or event handlers (onload, onerror, onmouseover, etc.). Example SQL: SELECT * FROM wishsuite_tables WHERE column LIKE '%<script%' OR column LIKE '%onerror=%'.
    Affected if Any records contain executable XSS payloads such as script tags or event handler attributes

A site is affected if WishSuite plugin versions below 1.3.8 are installed and active, with authenticated users able to submit content that gets stored in the plugin's database without sanitization.

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.3.8 or later
Fixed in 1.3.8
Interim mitigation

Update WishSuite to the latest patched version. Until patched, implement input validation and output encoding on user-supplied data, and consider deploying a WAF rule to block XSS payloads.

Recommended fix Moderate confidence

1.3.8

  1. Create a full backup of your WordPress site before making any changes
  2. Update the WishSuite plugin to version 1.3.8 or later through the WordPress admin dashboard (Plugins > Available Plugins > Update Now) or via wp-cli: wp plugin update wishsuite
  3. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
  4. Test core WishSuite functionality (adding items to wishlist, frontend display) to ensure the update did not break expected features
  5. Clear any server-side and CDN caches to ensure the patched version is served to users

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

Fix this in Wishsuite 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-2024-29927 — 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-29927 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