# CVE-2025-8518: givanz Vvveb Code Editor code.php save code injection

> Remote attackers with permissions can inject malicious code via the Code Editor save function, leading to arbitrary code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2025
- **Updated:** 5 Aug 2025
- **Also known as:** GHSA-6mmr-q9x7-2592

## What is CVE-2025-8518?

CVE-2025-8518 is a medium-severity code injection vulnerability in givanz Vvveb, published on 4 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in givanz Vvveb 1.0.5. It has been rated as critical. Affected by this issue is the function Save of the file admin/controller/editor/code.php of the component Code Editor. The manipulation leads to code injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.0.6 is able to address this issue. The name of the patch is f684f3e374d04db715730fc4796e102f5ebcacb2. It is recommended to upgrade the affected component.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-8518?

It affects 1 product.


Products: Vvveb Vvveb.

## How do I fix CVE-2025-8518?

No fix has been published for CVE-2025-8518 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8518 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8518 exists.

Public exploit code:

- Remote Code Execution Vulnerability in Vvveb (metasploit)
- This repository contains a Proof of Concept (PoC) demonstrating a critical vulnerability in givanz Vvveb 1.0.5. The vulnerability allows an authenticated user with template editing privileges to write arbitrary PHP code to server files, leading to Remote Code Execution (RCE). (github_poc): https://github.com/maestro-ant/Vvveb-CMS-CVE-2025-8518
- CVE-2025-8518 - Draft or TODO (github_poc): https://github.com/HORKimhab/CVE-2025-8518

## Other vulnerabilities in givanz Vvveb

- [CVE-2025-44022](https://insights.sbomify.com/CVE-2025-44022/): Code injection in n/a (critical 9.8)
- [CVE-2025-11028](https://insights.sbomify.com/CVE-2025-11028/): givanz Vvveb Image information disclosure (medium 6.9)
- [CVE-2025-12203](https://insights.sbomify.com/CVE-2025-12203/): givanz Vvveb Code Editor functions.php sanitizeFileName path traversal (medium 5.3)
- [CVE-2025-11029](https://insights.sbomify.com/CVE-2025-11029/): givanz Vvveb cross-site request forgery (medium 5.3)
- [CVE-2025-9728](https://insights.sbomify.com/CVE-2025-9728/): givanz Vvveb login.tpl cross site scripting (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8518 and fix it if it is affected.

What it is: CVE-2025-8518 is a medium-severity code injection vulnerability in givanz Vvveb, published on 4 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8518 exists.

Affected product: givanz Vvveb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8518/ (Markdown: https://insights.sbomify.com/CVE-2025-8518/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8518
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8518
- OSV: https://osv.dev/vulnerability/CVE-2025-8518

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8518/
Summaries are generated and may contain mistakes; the official description above is the record.