dbcve.org
Wp CrowdfundingWordPress extension · Themeum

CVE-2023-47532

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to after 2.1.6 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Themeum WP Crowdfunding plugin <= 2.1.6 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 confidence

Unauthenticated reflected cross-site scripting (XSS) vulnerability in Themeum WP Crowdfunding plugin versions 2.1.6 and below allows attackers to inject malicious scripts through unsanitized user input, likely via URL parameters, which then gets reflected back to victim users.

MitigationUpdate the Themeum WP Crowdfunding plugin to the latest version beyond 2.1.6 which contains the security patch, or implement proper input sanitization and output encoding on all user-supplied parameters in the plugin.

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
Wp CrowdfundingWordPress extension
Affected:<= 2.1.6

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Themeum WP Crowdfunding plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Themeum WP Crowdfunding' in the plugin list, or query the database wp_plugins table for the plugin folder name containing 'crowdfunding'.
    Affected if The plugin appears in the installed plugins list.
  2. Determine installed plugin version
    In WordPress admin > Plugins > Installed Plugins, locate 'Themeum WP Crowdfunding' and read the version number displayed beneath the plugin name. Alternatively, inspect the main plugin file header in wp-content/plugins/total-crowdfunding/ or similar path for the 'Version' tag.
    Affected if The version number is 2.1.6 or lower.
  3. Confirm plugin is active on the site
    In WordPress admin > Plugins > Installed Plugins, verify the plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'. Also check the site's frontend to confirm the crowdfunding functionality is present and accessible.
    Affected if The plugin is active and the crowdfunding features are accessible to visitors.
  4. Identify exposed crowdfunding endpoints
    Check the site's public-facing pages for URLs containing crowdfunding-related paths (typically /wp-content/plugins/total-crowdfunding/ or rewrite rules under /crowdfunding/). Use a crawler or check WordPress rewrite rules via admin > Settings > Permalinks and inspect for crowdfunding-related endpoints.
    Affected if Crowdfunding pages or endpoints are publicly accessible without authentication.
  5. Test URL parameters for reflected input
    Append common test strings to crowdfunding page URLs such as ?test=<script>alert(1)</script> or ?search=<img src=x onerror=alert(1)> and examine the page source to see if the input is reflected without encoding. Since specific vulnerable parameters are not identified, test any URL parameters used on crowdfunding pages.
    Affected if User-supplied URL parameters are reflected in the response without proper sanitization or encoding.

The site is affected if Themeum WP Crowdfunding plugin version 2.1.6 or lower is installed, active, and publicly accessible with exposed endpoints that reflect URL parameters back to users.

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.

From vendor data
Upgrade available Upgrade to a release after 2.1.6
Interim mitigation

Update the Themeum WP Crowdfunding plugin to the latest version beyond 2.1.6 which contains the security patch, or implement proper input sanitization and output encoding on all user-supplied parameters in the plugin.

Fix this in Wp Crowdfunding Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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