dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-15473

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-12
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 5 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 identified in Eleveo Call Recording Software 9.7.0. This issue affects some unknown processing of the file /callrec/restoreCallAction.do of the component Recorded Calls Page. The manipulation leads to improper authorization. The attack is possible to be carried out remotely. The exploit is publicly available and might 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 /callrec/restoreCallAction.do endpoint of the Recorded Calls Page component. This allows authenticated or potentially unauthenticated users to restore recorded calls without proper authorization checks, possibly exposing sensitive call recordings to unauthorized access.

MitigationSince the vendor did not respond to disclosure, implement compensating controls such as network segmentation to restrict access to the affected endpoint, deploy WAF rules to monitor and block suspicious restoreCallAction.do requests, and review application logs for unauthorized call restoration activity.

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
    Locate and identify the Eleveo Call Recording Software installation in your environment - check for the application directory, service, or web application root that hosts the call recording system
    Affected if Eleveo Call Recording Software is present and accessible in the environment
  2. Verify installed version is 9.7.0
    Check the application version information - typically found in the application header, about page, version file, or the software itself (often displayed in the UI footer or in configuration files within the installation directory)
    Affected if The installed version is exactly 9.7.0 or falls within the affected range around this version
  3. Locate the restoreCallAction.do endpoint
    Verify the presence of the /callrec/restoreCallAction.do endpoint by examining the application's web accessible paths or by attempting to access it (check the callrec directory within the web application)
    Affected if The /callrec/restoreCallAction.do endpoint exists and is accessible in the application
  4. Test authorization enforcement on the endpoint
    Attempt to access or invoke the restoreCallAction.do endpoint with different user roles - specifically test if an unauthenticated user or a user without proper restoration privileges can successfully trigger a call restoration action
    Affected if The endpoint allows call restoration without requiring proper authentication or authorization validation (the request succeeds without appropriate access controls)

Your environment is affected if Eleveo Call Recording Software version 9.7.0 is installed and the /callrec/restoreCallAction.do endpoint permits call restoration actions without proper authorization checks.

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

Since the vendor did not respond to disclosure, implement compensating controls such as network segmentation to restrict access to the affected endpoint, deploy WAF rules to monitor and block suspicious restoreCallAction.do requests, and review application logs for unauthorized call restoration activity.

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-15473 — 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-15473 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