dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-49270

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Mario Peshev WP-CRM System wp-crm-system allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WP-CRM System: from n/a through <= 3.4.2.

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

Missing Authorization vulnerability in the WP-CRM System WordPress plugin allows authenticated users to access functionality that should be constrained by Access Control Lists (ACLs). The plugin fails to properly verify user capabilities before executing certain functions, potentially allowing lower-privileged users to perform actions outside their intended permissions.

MitigationApply the vendor patch (upgrade to version 3.4.3 or later if available) which adds proper capability checks to constrain functionality to authorized user roles. Until patch is available, review admin functionality access controls and restrict via server-side configuration if possible.

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 checks

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

  1. Confirm WP-CRM System plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WP-CRM System' in the list. Note whether it is installed and whether it is activated.
    Affected if The plugin is installed and activated on the WordPress site.
  2. Identify installed WP-CRM System version
    In the Plugins list, find WP-CRM System and view the version number displayed under the plugin name. Alternatively, check the main plugin file header at /wp-content/plugins/wp-crm-system/includes/index.php or the main plugin file for the 'Version' header comment.
    Affected if The installed version is lower than 3.4.3.
  3. Review WordPress user roles with CRM access
    Go to Users > All Users in the WordPress admin. Examine each user account and note their assigned roles (Administrator, Editor, Subscriber, or custom roles). Pay particular attention to non-administrator roles that may have CRM-related capabilities.
    Affected if There are users with roles below Administrator who have access to WP-CRM System functionality.
  4. Inspect WP-CRM System capability settings
    Navigate to CRM > Settings > Access Control (or similar access-related settings page within the plugin). Check which roles are granted permissions for features like viewing contacts, managing deals, or accessing admin functions.
    Affected if Lower-privileged roles (such as Editor, Author, Subscriber, or custom roles) are granted elevated CRM capabilities that should be restricted to administrators.

A user is affected if the WP-CRM System plugin is installed and active with a version lower than 3.4.3 and non-administrator users have elevated CRM access permissions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (upgrade to version 3.4.3 or later if available) which adds proper capability checks to constrain functionality to authorized user roles. Until patch is available, review admin functionality access controls and restrict via server-side configuration if possible.

Recommended fix Moderate confidence

latest available version (version > 3.4.2)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP-CRM System plugin
  4. Check if an update is available for WP-CRM System
  5. If update available, click 'Update Now' to install the latest version
  6. Verify the update completes successfully
  7. Test that the plugin functionality works as expected after update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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