Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-15374

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

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
A flaw has been found in Eleveo Call Recording Software 9.7.0. This affects an unknown function of the file /callrec/roleAddAction.do of the component Group Interface. Executing a manipulation can lead to improper authorization. It is possible to launch the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

Eleveo Call Recording Software 9.7.0 contains an improper authorization vulnerability in the Group Interface component via the /callrec/roleAddAction.do endpoint. The flaw allows remote attackers to manipulate role assignment functions without proper authorization checks, potentially granting unauthorized access to administrative or privileged functions.

MitigationImplement role-based access control (RBAC) validation on the roleAddAction.do endpoint to verify user permissions before executing role modifications. If no vendor patch is available, consider network segmentation to restrict access to administrative interfaces and monitor for unauthorized role changes.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 Eleveo Call Recording Software installation and version
    Locate the Eleveo installation directory or check the software inventory for 'Eleveo Call Recording Software' and identify the installed version number. Common locations include /opt/eleveo or C:\Program Files\Eleveo. Check version via application GUI, startup logs, or configuration files.
    Affected if The installed version is exactly 9.7.0 or falls within the 9.7.x release line.
  2. Verify web interface accessibility
    Confirm the Eleveo web interface is accessible by attempting to reach the base URL (typically https://<hostname>/callrec or http://<hostname>:8080/callrec). Check if the application responds to HTTP/HTTPS requests.
    Affected if The Eleveo web interface is exposed and reachable on the network.
  3. Check roleAddAction.do endpoint existence
    Access the URL path /callrec/roleAddAction.do through the web browser or curl command to determine if the endpoint is present and responds.
    Affected if The endpoint returns any HTTP response (including error pages), indicating it exists and is accessible.
  4. Inspect role assignment configuration
    Review the application's role configuration files, typically found in the config or conf directory under the Eleveo installation path. Look for role definitions, user-to-role mappings, and permission settings related to roleAddAction.do.
    Affected if No role-based access control validation is configured for the roleAddAction.do endpoint, or the endpoint permits role modifications without privilege verification.

A user is affected if Eleveo Call Recording Software version 9.7.0 is installed, the web interface is accessible, and the /callrec/roleAddAction.do endpoint does not enforce proper authorization checks for role assignment operations.

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

Implement role-based access control (RBAC) validation on the roleAddAction.do endpoint to verify user permissions before executing role modifications. If no vendor patch is available, consider network segmentation to restrict access to administrative interfaces and monitor for unauthorized role changes.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15374 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15374 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