CVE-2026-15373
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 · uneditedA vulnerability was detected in Eleveo Call Recording Software 9.7.0. The impacted element is an unknown function of the file /callrec/userAddAction.do. Performing a manipulation of the argument role results in improper authorization. It is possible to initiate the attack remotely. The exploit is now public 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 confidenceEleveo Call Recording Software 9.7.0 contains an improper authorization vulnerability in /callrec/userAddAction.do. The role parameter can be manipulated during user creation to bypass authorization checks, potentially allowing unauthorized users to escalate privileges or create accounts with elevated roles.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Eleveo Call Recording Software installation and versionLocate Eleveo installation directory or check application startup/version information. Common locations include /opt/eleveo or C:\Program Files\Eleveo. Check for version.txt, about page, or application headers displaying version 9.7.0.Affected if Eleveo Call Recording Software version 9.7.0 is installed and running
-
Verify the vulnerable endpoint existsCheck if the web application exposes /callrec/userAddAction.do. This can be done by reviewing web server configuration files, checking the deployed WAR/webapp directory, or attempting to access the endpoint via HTTP request if you have authorized access to the application.Affected if The /callrec/userAddAction.do endpoint is present in the deployed application
-
Confirm user creation functionality is enabledReview the application configuration to determine if the user creation module (userAddAction.do) is active and not disabled. Check web.xml or application configuration files for servlet mappings related to userAddAction.Affected if The userAddAction.do servlet is actively mapped and enabled in the web application configuration
-
Inspect role assignment authorization logicExamine the application source code or decompiled classes for userAddAction.do to verify if server-side role validation is properly enforced. Look for authorization checks before processing the role parameter.Affected if The role parameter in user creation requests is not validated server-side against the authenticated user's permissions
You are affected if Eleveo Call Recording Software 9.7.0 is running with the /callrec/userAddAction.do endpoint accessible and the role parameter lacks proper server-side authorization validation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper server-side authorization validation before processing user creation requests. Validate that the authenticated user has permission to assign specific roles, and enforce role-based access control (RBAC) checks on the role parameter.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15373 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15373 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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