dbcve.org
Vip Video AnalysisApplication · Vip Video Analysis Project

CVE-2023-3015

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-31
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
A vulnerability has been found in yiwent Vip Video Analysis 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file data/title.php. The manipulation of the argument titurl leads to server-side request forgery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-230359.

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

A Server-Side Request Forgery (SSRF) vulnerability exists in yiwent Vip Video Analysis 1.0 in the data/title.php file. The 'titurl' parameter is not properly validated, allowing remote attackers to make the server perform arbitrary requests to internal or external resources, potentially exposing internal services and data.

MitigationImplement strict input validation and allowlisting for the 'titurl' parameter to restrict URLs to trusted domains only. If no vendor patch is available, consider disabling the affected functionality or deploying network segmentation to limit the impact of SSRF attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vip Video AnalysisApplication
Affected:= 1.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate the vulnerable PHP file
    Search the web server document root for the file 'data/title.php' that is part of the Vip Video Analysis application. Use file system search commands like 'find /var/www -name title.php' or similar depending on your server OS.
    Affected if The file data/title.php exists in the application directory and the application is Vip Video Analysis version 1.0
  2. Verify the application version
    Check the application version by looking for a version file, README, or any metadata in the Vip Video Analysis installation directory. Compare the installed version to '1.0' which is the only affected version listed.
    Affected if The installed version is exactly 1.0
  3. Confirm the vulnerable parameter exists
    Examine the data/title.php file source code and verify it accepts a 'titurl' GET or POST parameter. Look for code that uses this parameter to make server-side requests without proper validation.
    Affected if The 'titurl' parameter is present and used in server-side request operations without validated input filtering
  4. Test if the endpoint is exposed
    If the application is web-accessible, attempt to access data/title.php directly via HTTP/HTTPS to confirm the endpoint is reachable. Check if the application is behind authentication or network restrictions.
    Affected if The data/title.php endpoint is accessible without authentication and accepts the 'titurl' parameter in requests
  5. Inspect input validation in code
    Review the data/title.php source code for any input validation, allowlisting, or sanitization applied to the 'titurl' parameter before using it in request operations.
    Affected if No input validation or allowlisting is implemented for the 'titurl' parameter, allowing arbitrary URLs to be passed

The environment is affected if Vip Video Analysis version 1.0 is installed, the data/title.php file exists, and the 'titurl' parameter accepts unvalidated input that can trigger arbitrary server-side requests.

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

Implement strict input validation and allowlisting for the 'titurl' parameter to restrict URLs to trusted domains only. If no vendor patch is available, consider disabling the affected functionality or deploying network segmentation to limit the impact of SSRF attacks.

Fix this in Vip Video Analysis Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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