# CVE-2016-20079: WordPress Dharma Booking 2.28.3 Local File Inclusion via proccess.php

> Unauthenticated attackers can read sensitive files via local file inclusion in the Dharma Booking plugin by manipulating the gateway parameter.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-h9hw-9352-7j55

## What is CVE-2016-20079?

CVE-2016-20079 is a medium-severity path traversal vulnerability in jamie Dharma Booking, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WordPress Dharma Booking 2.28.3 and earlier contains a local file inclusion vulnerability that allows unauthenticated attackers to include arbitrary files by manipulating the gateway parameter. Attackers can supply file paths with directory traversal sequences or null byte injection to the gateway parameter in proccess.php to read sensitive files like configuration and system files.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2016-20079?


## How do I fix CVE-2016-20079?

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

## Is CVE-2016-20079 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20079 and fix it if it is affected.

What it is: CVE-2016-20079 is a medium-severity path traversal vulnerability in jamie Dharma Booking, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20079 exists.

Affected product: jamie Dharma Booking. 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-2016-20079/ (Markdown: https://insights.sbomify.com/CVE-2016-20079/index.md)
```

## Sources

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

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