WishsuiteWordPress extension · Hasthemes
CVE-2023-23731
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in HasTheme WishSuite plugin <= 1.3.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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the HasTheme WishSuite WordPress plugin versions 1.3.3 and below allows attackers to induce authenticated users to perform unintended actions by tricking them into submitting malicious 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
WishsuiteWordPress extension
< 1.3.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WishSuite plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the wishsuite folderAffected if The wishsuite folder exists in the plugins directory or the plugin appears in WordPress admin plugins list
-
Identify installed WishSuite versionIn WordPress admin, go to Plugins > Installed Plugins and find WishSuite - the version number is displayed below the plugin name. Alternatively, open wishsuite/wishsuite.php and check the 'Version' header in the plugin comment blockAffected if Version shown is 1.3.3 or lower, or if the version cannot be determined but the plugin is present
-
Verify plugin status is activeIn WordPress admin Plugins page, check if WishSuite shows as 'Active' under the plugin status columnAffected if Plugin is active (inactive plugins would not expose authenticated users to the CSRF vulnerability)
User is affected if WishSuite plugin is installed, active, and running version 1.3.3 or below (any version prior to 1.3.4).
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.4
Update the WishSuite plugin to a version beyond 1.3.3 which includes proper anti-CSRF token validation on state-changing operations.
Wishsuite version 1.3.4 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the WishSuite plugin in the list
- Check if the current version is below 1.3.4
- If vulnerable, click 'Update Now' on the WishSuite plugin to update to version 1.3.4 or latest available version
- Alternatively, download the latest version from the WordPress plugin repository or from HasTheme and upload it manually via Plugins > Add New > Upload Plugin
- After update, verify the installed version is 1.3.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wishsuite
Scoped from the published advisory
- Consultation1.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23731 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23731 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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