# CVE-2025-34103: WePresent WiPG-1000 Unauthenticated Command Injection in via rdfs.cgi

> Unauthenticated attackers can execute arbitrary commands on WePresent WiPG-1000 devices via the rdfs.cgi endpoint.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-7q8c-7g45-2m2q

## What is CVE-2025-34103?

CVE-2025-34103 is a critical command injection vulnerability in WePresent (Barco) WiPG-1000, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated command injection vulnerability exists in WePresent WiPG-1000 firmware versions prior to 2.2.3.0, due to improper input handling in the undocumented /cgi-bin/rdfs.cgi endpoint. The Client parameter is not sanitized before being passed to a system call, allowing an unauthenticated remote attacker to execute arbitrary commands as the web server user.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-34103 being exploited?

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

Public exploit code:

- WePresent WiPG-1000 Command Injection (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34103 is a critical command injection vulnerability in WePresent (Barco) WiPG-1000, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34103 exists.

Affected product: WePresent (Barco) WiPG-1000. 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-34103/ (Markdown: https://insights.sbomify.com/CVE-2025-34103/index.md)
```

## Sources

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

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