dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13093

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-13
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
The Devs CRM – Manage tasks, attendance and teams all together plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the '/wp-json/devs-crm/v1/bulk-update' REST-API endpoint in all versions up to, and including, 1.1.8. This makes it possible for unauthenticated attackers to update leads tags.

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 · high confidence

The Devs CRM WordPress plugin registers a REST API endpoint at /wp-json/devs-crm/v1/bulk-update that processes lead tag modifications without verifying user authorization. The endpoint lacks a permission_callback function, allowing any unauthenticated request to modify lead data via the bulk-update functionality.

MitigationUpdate to version 1.1.9 or later when available. Until then, consider disabling the plugin or implementing firewall rules to restrict access to the /wp-json/devs-crm/ 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
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. Verify Devs CRM plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Devs CRM' in the list. Alternatively, check the /wp-content/plugins/ directory for a devs-crm folder.
    Affected if The plugin is present in the plugins directory, regardless of activation status
  2. Check the installed plugin version
    In WordPress admin, click on the Devs CRM plugin to view its details, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block.
    Affected if The installed version is lower than 1.1.9 or the version cannot be determined (treat as vulnerable)
  3. Test for unauthenticated API access
    Send a crafted HTTP request to your site's /wp-json/devs-crm/v1/bulk-update endpoint without providing authentication credentials (no cookies, no Authorization header). Use a tool like curl: curl -X POST https://your-site.com/wp-json/devs-crm/v1/bulk-update -H "Content-Type: application/json" -d '{}'
    Affected if The endpoint returns a valid JSON response (not a 401 Unauthorized or 403 Forbidden error), indicating the request was processed without authentication
  4. Confirm the permission_callback is missing
    Examine the plugin source code in the main PHP file to locate the register_rest_route call for /devs-crm/v1/bulk-update. Check if the 'permission_callback' argument is defined.
    Affected if The register_rest_route call for bulk-update does not include a permission_callback, or the callback always returns true

A user is affected if the Devs CRM plugin is installed with a version prior to 1.1.9 AND the /wp-json/devs-crm/v1/bulk-update endpoint responds to unauthenticated requests without returning an authorization error.

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

Update to version 1.1.9 or later when available. Until then, consider disabling the plugin or implementing firewall rules to restrict access to the /wp-json/devs-crm/ endpoints.

Recommended fix Moderate confidence

Version 1.1.9 or higher

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'The Devs CRM – Manage tasks, attendance and teams all together' plugin
  4. Click 'Update now' if an update is available, or manually upload version 1.1.9 or higher from wordpress.org/plugins/devs-crm
  5. Verify the update completed successfully

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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