dbcve.org
VvvebApplication

CVE-2025-9397

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-24
Fix available
A fix is available. Upgrade to after 1.0.7.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 weakness has been identified in givanz Vvveb up to 1.0.7.2. Affected is an unknown function of the file /system/traits/media.php. Executing manipulation of the argument files[] can lead to unrestricted upload. The attack can be launched remotely. The exploit has been made available to the public and could be exploited. Applying a patch is advised to resolve this issue. The code maintainer explains, that "[he] fixed the code to remove this vulnerability and will make a new release".

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 critical unrestricted file upload vulnerability exists in Vvveb CMS up to version 1.0.7.2 within /system/traits/media.php. Attackers can manipulate the files[] parameter to upload arbitrary files to the server without proper validation, potentially achieving remote code execution.

MitigationApply the vendor patch to /system/traits/media.php to implement proper file type validation, content inspection, filename sanitization, and secure storage outside web-accessible directories.

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
VvvebApplication
Affected:<= 1.0.7.2

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. Confirm Vvveb CMS installation and version
    Locate the version file or admin dashboard that displays the installed Vvveb version. Check the main version indicator or composer.json/changelog for the exact version number.
    Affected if The installed version is 1.0.7.2 or any earlier version.
  2. Verify vulnerable file exists
    Check if the file /system/traits/media.php exists on the web server filesystem. This file contains the unrestricted upload vulnerability.
    Affected if The file /system/traits/media.php exists on the server.
  3. Identify file upload endpoint exposure
    Determine if the media upload functionality is web-accessible. Look for endpoints that accept the files[] parameter, typically in admin panels or media management sections.
    Affected if The upload functionality accepting files[] parameter is accessible without proper authentication or validation.
  4. Inspect upload directories for unauthorized files
    Review common upload directories (such as /media/, /uploads/, or custom paths configured in media.php) for unexpected file types, especially executable files (php, phtml, phar), scripts, or web shells.
    Affected if Unexpected executable files, scripts, or unfamiliar file types are present in upload directories.
  5. Check web server access logs
    Review web server access logs for POST requests to media.php or upload endpoints containing files[] parameter from unusual IP addresses or automated tools.
    Affected if Requests with files[] parameter are present in logs from unauthorized sources or show anomalous upload patterns.

A system is affected if it runs Vvveb CMS version 1.0.7.2 or earlier, has the vulnerable /system/traits/media.php file accessible, and the file upload feature using the files[] parameter is exposed without proper validation.

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
Upgrade available Upgrade to a release after 1.0.7.2
Interim mitigation

Apply the vendor patch to /system/traits/media.php to implement proper file type validation, content inspection, filename sanitization, and secure storage outside web-accessible directories.

Recommended fix Moderate confidence
  1. Obtain the patched version of /system/traits/media.php from the maintainer or the project's issue tracker where the fix was committed
  2. Replace the vulnerable /system/traits/media.php file with the patched version
  3. Verify that the patch properly validates the files[] parameter to prevent unrestricted file uploads
  4. Ensure proper authentication and authorization checks are in place before allowing file uploads
  5. Test the file upload functionality to confirm the vulnerability is mitigated
  6. If available, review the commit or diff to ensure all access control improvements are applied

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

Fix this in Vvveb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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