CVE-2025-47690
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 Smackcoders Inc., Lead Form Data Collection to CRM wp-leads-builder-any-crm allows Privilege Escalation.This issue affects Lead Form Data Collection to CRM: from n/a through <= 3.1.
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 confidenceThe wp-leads-builder-any-crm WordPress plugin (versions <= 3.1) contains a missing authorization vulnerability that allows authenticated users to perform actions beyond their intended privilege level, enabling privilege escalation. An attacker with minimal user access (such as a subscriber) can potentially execute administrative functions due to insufficient capability checks on certain plugin endpoints.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify plugin installation status and versionNavigate to WordPress admin > Plugins > Installed Plugins and locate 'wp-leads-builder-any-crm'. Note the version number displayed next to the plugin name. Alternatively, check the plugin files in wp-content/plugins/ for a version marker in the main plugin file.Affected if The plugin is installed and the version is unknown or falls within any version range that lacks proper authorization checks (verify against official plugin changelog for patch dates).
-
Confirm plugin is activeIn the same Plugins admin screen, verify whether the plugin shows as 'Active'. Only active instances can be exploited.Affected if The plugin is active and running.
-
Audit user role assignments for the pluginGo to Users > All Users in WordPress admin. Review which users are assigned roles that include access to the plugin features (typically Subscriber, Contributor, or custom roles). Check if any low-privilege users have been granted CRM-related capabilities.Affected if Low-privilege users (Subscriber, Contributor, or custom roles with limited permissions) have access to the plugin or its CRM functionality.
-
Check for unauthorized admin actions or CRM data accessReview WordPress activity logs, audit logs, or security logs for actions performed by non-administrator users that modify system settings, create new administrator accounts, or access CRM lead data outside their normal permissions. Also check user capability tables in the database for unexpected additions.Affected if Any evidence exists of low-privilege users performing administrative actions or accessing CRM data they should not have permission to access.
Your environment is affected if the wp-leves-builder-any-crm plugin is installed and active, and low-privilege users have any form of access to its CRM functionality or have performed actions beyond their assigned role permissions.
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 the plugin to the latest version which includes proper authorization checks, or implement WordPress capability checks (using current_user_can()) and nonce verification on all sensitive plugin actions to ensure users can only access functions appropriate to their role.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47690 — 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-2025-47690 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