dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-22374

MEDIUM · 6.0 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 →
66/100
Remediation priority · Elevated
Remotely reachable 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
A Server-Side Request Forgery (SSRF) vulnerability was discovered in the videx-legacy-ssl web service of Videx’s CyberAudit-Web, affecting versions prior to 1.1.3. This vulnerability has been patched in versions after 1.1.3. Leaving this vulnerability unpatched could lead to unauthorized access to the underlying infrastructure.

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

This is a Server-Side Request Forgery (SSRF) vulnerability in the videx-legacy-ssl web service component of Videx CyberAudit-Web. The vulnerability allows attackers to induce the web service to make unintended requests to internal infrastructure, potentially bypassing network restrictions and accessing sensitive internal systems or services.

MitigationUpgrade CyberAudit-Web to version 1.1.3 or later to apply the patched code that addresses this SSRF vulnerability.

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

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/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 if CyberAudit-Web is installed
    Search for CyberAudit-Web software on the system, check installed programs or services list, or look for Videx-related directories in common installation paths
    Affected if The software is not found or this product is not in use
  2. Determine the installed version of CyberAudit-Web
    Check the application version through its web interface login page, check version files in the installation directory, or review application logs that may contain version information
    Affected if The installed version is unknown or cannot be determined from available sources
  3. Verify the videx-legacy-ssl component is present
    Examine the CyberAudit-Web installation directory for the videx-legacy-ssl module or component, or check the web service configuration files for references to legacy-ssl
    Affected if The videx-legacy-ssl component exists in the installation
  4. Confirm the web service is running and network-accessible
    Check if the CyberAudit-Web web service is actively running and accessible over the network, verify the service is listening on its configured HTTP/HTTPS port
    Affected if The web service is running and externally or internally accessible
  5. Compare installed version to the fixed version
    Compare the identified CyberAudit-Web version against the vulnerable range (all versions prior to 1.1.3). If version 1.1.3 or later is confirmed, the environment is not affected
    Affected if The installed version is below 1.1.3 (for example: 1.1.2, 1.1.0, 1.0.x, or any earlier version)

The environment is affected if Videx CyberAudit-Web with the videx-legacy-ssl component is installed and the version is below 1.1.3, as this SSRF vulnerability exists in all prior versions.

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 version 1.1.3 or later to apply the patched code that addresses this SSRF vulnerability.

Recommended fix High confidence

Version 1.1.3 or later of Videx CyberAudit-Web

  1. 1. Identify the current version of Videx CyberAudit-Web (videx-legacy-ssl) by checking the software documentation or system inventory
  2. 2. If the current version is prior to 1.1.3, plan for an upgrade to version 1.1.3 or later
  3. 3. Before upgrading, review any release notes and backup the current system configuration and data
  4. 4. Perform the upgrade following the vendor's official upgrade procedure for CyberAudit-Web
  5. 5. After upgrading, verify that the videx-legacy-ssl web service is running the patched version (1.1.3 or later)
  6. 6. Test that the SSRF vulnerability is no longer exploitable by confirming the fix addresses the Server-Side Request Forgery issue

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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