# CVE-2022-47879: A Remote Code Execution (RCE) vulnerability in /be/rpc.php in Jedox 2020.2.5 allows remote authenticated users to load arbitrary PHP classes


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 May 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-hvp3-qrpc-r6hh

## What is CVE-2022-47879?

CVE-2022-47879 is a high-severity vulnerability in n/a, published on 12 May 2023. 

### Official description

A Remote Code Execution (RCE) vulnerability in /be/rpc.php in Jedox 2020.2.5 allows remote authenticated users to load arbitrary PHP classes from the 'rtn' directory and execute its methods. NOTE: The vendor states that the vulnerability affects installations running version 22.5 or earlier. The issue was resolved with version 23.2 and later versions are not affected.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-47879?

It affects 2 products.


Products: Jedox Jedox, Jedox Jedox Cloud.

## How do I fix CVE-2022-47879?

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

## Is CVE-2022-47879 being exploited?

There is no known exploitation of CVE-2022-47879 in the wild and no public exploit code.

Public exploit code:

- Jedox 2022.4.2 - Code Execution via RPC Interfaces (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-47877](https://insights.sbomify.com/CVE-2022-47877/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2022-47876](https://insights.sbomify.com/CVE-2022-47876/): Code injection in n/a (critical 9.1)
- [CVE-2022-47878](https://insights.sbomify.com/CVE-2022-47878/): File upload in n/a (critical 9.1)
- [CVE-2022-47880](https://insights.sbomify.com/CVE-2022-47880/): Information disclosure in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47879 and fix it if it is affected.

What it is: CVE-2022-47879 is a high-severity vulnerability in n/a, published on 12 May 2023. 
Exploitation: There is no known exploitation of CVE-2022-47879 in the wild and no public exploit code.

Affected product: n/a. 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-2022-47879/ (Markdown: https://insights.sbomify.com/CVE-2022-47879/index.md)
```

## Sources

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

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