dbcve.org
Wp CrowdfundingWordPress extension · Themeum

CVE-2023-50859

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-28
Fix available
A fix is available. Upgrade to after 2.1.6 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 Themeum WP Crowdfunding allows Stored XSS.This issue affects WP Crowdfunding: from n/a through 2.1.6.

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 Themeum WP Crowdfunding plugin allows authenticated attackers to inject malicious JavaScript through unsanitized user input, which is then stored in the database and executed when other users view affected pages.

MitigationUpdate WP Crowdfunding to the latest version. Until then, restrict user registration and manually review existing user-submitted content for malicious scripts.

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
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 WP Crowdfunding plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Themeum WP Crowdfunding' or check the plugin files in /wp-content/plugins/ for the wp-crowdfunding folder
    Affected if The plugin is not installed on the WordPress site
  2. Identify installed plugin version
    In WordPress admin > Plugins, click on the WP Crowdfunding plugin to view its version number, or open the main plugin file and look for the Version header in the plugin comments
    Affected if Version is 2.1.6 or lower (any version <= 2.1.6)
  3. Check if WordPress user registration is enabled
    In WordPress admin > Settings > General, verify if the 'Membership: Anyone can register' option is checked
    Affected if User registration is enabled, allowing authenticated attackers to register and inject malicious content
  4. Inspect database for user-submitted content
    Query the wp_postmeta and wp_posts tables (or custom tables prefixed wp_crowdfunding_) for campaign entries created by users; examine the meta values for unsanitized HTML or script tags
    Affected if User-submitted campaign data contains raw unsanitized input with script tags or javascript: URIs

You are affected if the WP Crowdfunding plugin version is 2.1.6 or lower AND user registration is enabled (or there are existing non-admin users) and their submitted content contains executable script tags.

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 a release after 2.1.6
Interim mitigation

Update WP Crowdfunding to the latest version. Until then, restrict user registration and manually review existing user-submitted content for malicious scripts.

Recommended fix Moderate confidence

WP Crowdfunding version 2.1.7 or latest available version

  1. 1. Back up your WordPress database and files before making any changes.
  2. 2. Navigate to your WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Find 'Wp Crowdfunding' (by Themeum) in the plugin list.
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version.
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin is functioning correctly on your campaign pages.

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

Fix this in Wp Crowdfunding Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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