dbcve.org
Wp CrowdfundingWordPress extension · Themeum

CVE-2023-41870

HIGH · 8.8 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 2.1.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Missing Authorization vulnerability in Themeum WP Crowdfunding allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Crowdfunding: from n/a through 2.1.5.

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

A Missing Authorization vulnerability in Themeum WP Crowdfunding plugin versions through 2.1.5 allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to privileged functionality without proper authentication.

MitigationImplement proper authorization checks and role-based access controls (RBAC) across all sensitive functionalities in the WP Crowdfunding plugin to ensure users can only access resources and actions appropriate to their privilege level.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Themeum WP Crowdfunding plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Themeum WP Crowdfunding' in the list, or check the /wp-content/plugins/ directory for the crowdfunding folder
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the plugin name to view details, or inspect the main plugin file (e.g., wp-crowdfunding.php) for the 'Version' header comment
    Affected if The version number is less than 2.1.6 (e.g., 2.1.5, 2.1.4, etc.)
  3. Identify exposed API endpoints or admin pages
    Review WordPress REST API routes registered by the plugin by accessing /wp-json/ and searching for 'crowdfunding' endpoints, or check the plugin source for add_action('rest_api_init') calls
    Affected if Any crowdfunding-related REST endpoints or admin AJAX actions are accessible without capability checks or require only a valid user session without proper role verification
  4. Inspect plugin capability checks
    Examine plugin PHP files for current_user_can() calls or similar authorization logic around sensitive functions (campaign creation, dashboard access, submission handling)
    Affected if Missing or insufficient capability checks are found before executing privileged operations

If the Themeum WP Crowdfunding plugin version is below 2.1.6 and sensitive endpoints or admin functions lack proper authorization verification, the environment is affected by this missing authorization vulnerability.

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

Implement proper authorization checks and role-based access controls (RBAC) across all sensitive functionalities in the WP Crowdfunding plugin to ensure users can only access resources and actions appropriate to their privilege level.

Recommended fix High confidence

2.1.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP Crowdfunding in the plugin list
  4. Check the current version - if below 2.1.6, an update is needed
  5. Click 'Update Now' to upgrade to version 2.1.6
  6. Alternatively, download version 2.1.6 from the official WordPress plugin repository or Themeum's website
  7. If automatic update fails, deactivate the current plugin, delete it, then upload and install version 2.1.6
  8. After upgrading, verify the plugin is functioning correctly and test that authorization controls are properly enforced

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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