CVE-2024-34758
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 · uneditedMissing Authorization vulnerability in Wpmet WP Fundraising Donation and Crowdfunding Platform.This issue affects WP Fundraising Donation and Crowdfunding Platform: from n/a through 1.6.4.
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 confidenceMissing Authorization vulnerability in Wpmet WP Fundraising Donation and Crowdfunding Platform allows unauthenticated or unauthorized users to access sensitive functionality or perform actions without proper permission checks. This is a broken access control issue where the plugin fails to verify user capabilities before executing certain operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Fundraising Donation plugin is installedCheck your WordPress plugins directory or access Plugins > Installed Plugins in the admin dashboard. Look for 'WP Fundraising Donation and Crowdfunding Platform' or 'WP Fundraising' in the plugin list.Affected if The plugin is present in the installation
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on the plugin to view details, or check the plugin's main PHP file header for the Version constant. Compare the version number to the fixed version 1.6.5.Affected if The installed version is lower than 1.6.5 or the version cannot be determined
-
Confirm the plugin is activeIn WordPress admin > Plugins > Installed Plugins, verify the plugin status shows as 'Active'. An inactive plugin would not be exploitable.Affected if The plugin is currently active on the site
-
Audit user accounts and roles for unauthorized accessReview Users > All Users in WordPress admin. Look for suspicious new administrator accounts or unexpected user registrations that could indicate the vulnerability was exploited. Check User Roles under each account.Affected if Unexpected user accounts exist, especially administrator-level accounts not created by known administrators
-
Review donation campaigns for unauthorized modificationsAccess the plugin's campaign management section (typically under Fundraising > All Campaigns). Check for campaigns created or modified by unknown users, or with altered settings.Affected if Campaigns exist that were not created by authorized administrators or show unauthorized changes
Your environment is affected if the WP Fundraising Donation and Crowdfunding Platform plugin is installed, active, and running at a version lower than 1.6.5.
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.
From vendor dataUpdate WP Fundraising Donation and Crowdfunding Platform to the latest version (1.6.5 or later) which should include proper authorization checks. Review user roles and permissions after updating.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34758 — 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-2024-34758 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