CVE-2025-49987
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 WPFactory CRM ERP Business Solution crm-erp-business-solution allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CRM ERP Business Solution: from n/a through <= 1.13.
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 WPFactory CRM ERP Business Solution WordPress plugin has a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This likely permits unauthenticated or unauthorized users to access sensitive CRM functionality or perform actions without proper capability checks.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if WPFactory CRM plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WPFactory CRM ERP Business Solution' or check the plugin files in /wp-content/plugins/ for a folder containing 'crm' or 'wpfactory-crm' in the nameAffected if The plugin is installed and active in the WordPress environment
-
Check installed plugin versionIn WordPress adminPlugins list, find the version listed under the plugin name, or open the main plugin PHP file and look for the 'Version' header in the plugin comment blockAffected if Version is 1.13 or lower (the vulnerability affects versions up to and including 1.13)
-
Inspect plugin for sensitive AJAX or REST endpointsExamine the plugin directory for files containing 'wp_ajax_' or 'wp_rest_' hooks, or check admin-ajax.php and WP REST API for plugin-prefixed endpoints (common paths: /wp-admin/admin-ajax.php?action=... or /wp-json/.../...)Affected if The plugin exposes AJAX or REST endpoints that handle sensitive CRM operations without visible capability checks
-
Test unauthorized access to CRM functionsAttempt to access suspected sensitive plugin URLs or trigger actions without logging in or without administrator capabilities - check for HTTP 200 responses on sensitive operations when unauthenticatedAffected if Sensitive CRM functionality is accessible to unauthenticated users or users lacking proper capabilities (e.g., subscribers, guests can access admin functions)
Environment is affected if the WPFactory CRM ERP Business Solution plugin version is 1.13 or lower and sensitive CRM endpoints are accessible without proper authentication or capability verification.
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 a version beyond 1.13 which contains the authorization fix, or audit affected endpoints and add proper capability checks (current_user_can) and nonce validations to all sensitive functions.
- 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-2025-49987 — 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-49987 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