dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2024-13175

MEDIUM · 5.5 CVSS v3.1 Published 2025-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Authorization Bypass Through User-Controlled Key vulnerability in Vidco Software VOC TESTER allows Forceful Browsing. This issue affects VOC TESTER: before 12.41.0.

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

Vidco Software VOC TESTER contains an authorization bypass vulnerability where a user-controlled key (likely an identifier or parameter) allows attackers to bypass access controls and perform forceful browsing to access unauthorized resources or pages. This is a classic IDOR (Insecure Direct Object Reference) pattern where improper authorization validation on user-supplied input enables access to functionality or data outside the user's intended permissions.

MitigationUpgrade to VOC TESTER version 12.41.0 or later. If immediate patching is not possible, implement proper authorization checks on all endpoints and validate that users can only access resources within their authorized scope.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Check installed VOC TESTER version
    Locate the VOC TESTER application and determine its version number (check application metadata, about dialog, or installation files)
    Affected if Version is lower than 12.41.0
  2. Identify endpoints with user-controlled parameters
    Review application URLs and API endpoints for parameters that accept user input such as IDs, keys, or object references
    Affected if Any endpoint accepts user-controlled identifiers without authorization validation
  3. Test authorization on parameter-based access
    Attempt to access resources by manipulating parameter values (IDs, keys) and verify whether the application validates user permissions for that specific resource
    Affected if The application allows accessing resources by modifying parameter values without verifying user permissions
  4. Inspect direct object reference patterns
    Examine code or configuration for patterns where user input directly references internal objects or records without permission checks
    Affected if User input is used directly to access objects or data without authorization validation

If VOC TESTER version is below 12.41.0 and the application has endpoints accepting user-controlled parameters that lack proper authorization checks, the environment is affected by this IDOR vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to VOC TESTER version 12.41.0 or later. If immediate patching is not possible, implement proper authorization checks on all endpoints and validate that users can only access resources within their authorized scope.

Recommended fix Moderate confidence

Version 12.41.0 or later

  1. 1. Identify the current version of Vidco Software VOC TESTER installed in your environment
  2. 2. Obtain the updated version 12.41.0 or later from the official vendor (Vidco Software)
  3. 3. Plan and schedule the upgrade during a maintenance window
  4. 4. Back up any existing configurations and data for the VOC TESTER application
  5. 5. Upgrade VOC TESTER to version 12.41.0 or latest available version
  6. 6. Verify the upgrade was successful by checking the new version number
  7. 7. Test that the authorization mechanisms work correctly and the IDOR vulnerability is remediated
  8. 8. Monitor the application for any unexpected behavior after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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