# CVE-2026-5336: Dataverse Integration < 2.91 - Contributor+ Server-Side Template Injection (SSTI) to Information Disclosure

> Contributors can exploit Server-Side Template Injection to disclose sensitive information, including session cookies of higher-privileged users.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-rrm7-wv5p-525q

## What is CVE-2026-5336?

CVE-2026-5336 is a medium-severity code injection vulnerability in Unknown DataPress (Dataverse Integration), published on 6 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The DataPress (Dataverse Integration) WordPress plugin before 2.91 does not properly restrict access to its template rendering feature and exposes the viewing user's data to it, allowing users with a role as low as Contributor to disclose sensitive information, such as the session cookies of higher privileged users who view the affected content.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-5336?


## How do I fix CVE-2026-5336?

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

## Is CVE-2026-5336 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5336 and fix it if it is affected.

What it is: CVE-2026-5336 is a medium-severity code injection vulnerability in Unknown DataPress (Dataverse Integration), published on 6 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5336 exists.

Affected product: Unknown DataPress (Dataverse Integration). 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-2026-5336/ (Markdown: https://insights.sbomify.com/CVE-2026-5336/index.md)
```

## Sources

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

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