dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-22375

CRITICAL · 9.3 CVSS v4.0 Published 2025-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An authentication bypass vulnerability was found in Videx's CyberAudit-Web. Through the exploitation of a logic flaw, an attacker could create a valid session without any credentials. This vulnerability has been patched in versions later than 9.5 and a patch has been made available to all instances of CyberAudit-Web, including the versions that are End of Maintenance (EOM). Anyone that requires support with the resolution of this issue can contact [email protected] for assistance.

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 · high confidence

Videx CyberAudit-Web contains an authentication bypass vulnerability where a logic flaw allows attackers to create valid sessions without any credentials. This enables unauthenticated attackers to gain full access to the application as if they were legitimate users.

MitigationUpgrade CyberAudit-Web to versions later than 9.5. For End of Maintenance versions, contact [email protected] to obtain the available patch.

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
None
Authentication
Y
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:A/V:D/RE:L/U:Green

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. Identify installed CyberAudit-Web version
    Locate the application version information in the software installation directory, about page, or system inventory. Common locations include version files, registry entries, or the application's admin interface.
    Affected if Version is 9.5 or lower (including any 9.x.x release up to 9.5)
  2. Confirm web interface is accessible
    Verify the CyberAudit-Web web interface is reachable on its configured port (typically 80/443 or custom). Attempt to access the login page or API endpoints.
    Affected if The web interface is exposed and responding, creating the attack surface for the bypass
  3. Check authentication configuration
    Examine the authentication configuration files or settings within CyberAudit-Web to determine if default authentication mechanisms are in use. Look for session management or login-related configuration.
    Affected if Default authentication configuration is active without additional hardening measures
  4. Test for session creation behavior
    If permitted in your environment, observe whether valid session tokens can be generated without providing credentials through the web interface login flow.
    Affected if Sessions can be created without valid credentials, confirming the bypass is exploitable

If CyberAudit-Web version 9.5 or lower is running with an accessible web interface, the authentication bypass vulnerability is present.

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 CyberAudit-Web to versions later than 9.5. For End of Maintenance versions, contact [email protected] to obtain the available patch.

Recommended fix Moderate confidence

Any version newer than 9.5 (contact Videx support for the exact recommended release)

  1. Contact Videx support at [email protected] to request the specific patch or upgrade package for your CyberAudit-Web version
  2. Confirm your current CyberAudit-Web version with your system documentation or system administrator
  3. Apply the provided patch or upgrade to a version newer than 9.5 as directed by Videx support
  4. After applying the fix, verify that authentication is required to create a valid session
  5. Test that the authentication bypass vulnerability is no longer exploitable
Caveat Contact Videx support to confirm compatibility with your specific deployment and any dependent systems

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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