dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-15376

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 vulnerability was found in Eleveo Call Recording Software 9.7.0. Affected is an unknown function of the file /callrec/statisticReportAction.do. The manipulation results in improper authorization. The attack can be launched remotely. The exploit has been made public and could 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

The vulnerability is an improper authorization flaw in Eleveo Call Recording Software 9.7.0's web interface, specifically affecting the /callrec/statisticReportAction.do endpoint. This broken access control likely allows unauthenticated or unauthorized users to access sensitive statistical reporting functions that should be restricted to privileged users. The exploit has been publicly disclosed, making this immediately actionable for attackers.

MitigationImplement proper function-level access controls on the affected endpoint, enforce authentication requirements, and restrict access to statistical reporting functions to authorized roles only. Consider web application firewall rules as a temporary measure while developing a comprehensive authorization fix.

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 is installed
    Check your system for Eleveo Call Recording Software installation directories, services, or application listings. Look for the 'Eleveo' or 'Call Recording' software components on the host.
    Affected if The software is installed on the system.
  2. Verify the installed version
    Locate the version information for the Eleveo Call Recording Software installation. This may be in the application itself, an about page, installed programs list, or configuration files. Compare your version to 9.7.0.
    Affected if The installed version is 9.7.0.
  3. Confirm web interface accessibility
    Identify if the Eleveo web interface port is open and accessible on your network. Common ports include 80, 443, or custom ports configured during installation. Attempt to reach the base web URL.
    Affected if The Eleveo web interface is accessible over the network.
  4. Test the affected endpoint without authentication
    Using a web browser or HTTP tool, navigate directly to the endpoint /callrec/statisticReportAction.do on your Eleveo server. Observe whether the page loads or returns data without requiring login credentials.
    Affected if The endpoint loads or returns any response (including error pages revealing system information) without authentication.
  5. Check for unauthorized access to statistical data
    If the endpoint responds, examine whether sensitive statistical reporting data, call records, user statistics, or administrative information is displayed or returned without proper authorization.
    Affected if Statistical reporting data or sensitive information is accessible without authenticated access.

A user is affected if Eleveo Call Recording Software version 9.7.0 is installed and the /callrec/statisticReportAction.do endpoint is accessible without authentication, exposing statistical reporting functions.

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 proper function-level access controls on the affected endpoint, enforce authentication requirements, and restrict access to statistical reporting functions to authorized roles only. Consider web application firewall rules as a temporary measure while developing a comprehensive authorization fix.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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