dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13092

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 access of data due to a missing capability check on the /wp-json/devs-crm/v1/attendances REST API Endpoint in all versions up to, and including, 1.1.8. This makes it possible for unauthenticated attackers to retrieve private user data, including password hashes.

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 has a REST API endpoint (/wp-json/devs-crm/v1/attendances) that lacks capability/authorization checks, allowing any unauthenticated user to access sensitive attendance data including private user information and password hashes.

MitigationUpdate the plugin to version 1.1.9 or later which includes proper capability checks on the REST API endpoint. If no update is available, disable the plugin until a patched version is released.

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 checks

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

  1. Verify the Devs CRM plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Devs CRM' in the list of installed plugins, or check the /wp-content/plugins/ directory for the devs-crm folder
    Affected if The Devs CRM plugin is present on the WordPress site
  2. Determine the installed plugin version
    In WordPress admin > Plugins, click on the Devs CRM plugin to view its details and version number, or read the main plugin PHP file header for the Version field
    Affected if The installed version is lower than 1.1.9 or the version cannot be determined
  3. Test unauthenticated access to the vulnerable endpoint
    Using a browser or curl, navigate to https://your-site.com/wp-json/devs-crm/v1/attendances without logging in
    Affected if The endpoint returns HTTP 200 with JSON data containing attendance records, user information, or any sensitive data without requiring authentication
  4. Inspect response for sensitive data exposure
    Examine the JSON response from the /wp-json/devs-crm/v1/attendances endpoint for fields such as user private details, personal information, or password-related data
    Affected if The response contains private user data, password hashes, or other sensitive attendance information accessible without credentials

The site is affected if the Devs CRM plugin is installed with a version below 1.1.9 and the /wp-json/devs-crm/v1/attendances endpoint returns sensitive data without requiring authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.1.9 or later which includes proper capability checks on the REST API endpoint. If no update is available, disable the plugin until a patched version is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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