Security readout for executives and security teams
Plain-English summary
CVE-2016-20079 affects the WordPress Dharma Booking plugin, version 2.28.3 and earlier. An unauthenticated attacker may manipulate a plugin parameter to include local files, potentially exposing sensitive configuration or system files. Public exploit information exists, but the provided sources do not show active exploitation or a named vendor patch.
Executive priority
Prioritize if Dharma Booking is present on public WordPress sites. The main business risk is exposure of sensitive files that may contain credentials or configuration secrets. If the plugin is not deployed, no action is needed beyond documenting non-exposure.
Technical view
The issue is a local file inclusion in proccess.php via the gateway parameter. Sources describe directory traversal and null byte injection enabling arbitrary local file inclusion or file reads. It is classified as CWE-98. The supplied CVSS 4.0 vector is 6.9 medium, although the vector lists local attack vector despite the web parameter description.
Likely exposure
Exposure is likely limited to WordPress sites with Dharma Booking installed, especially version 2.28.3 or earlier. Internet-facing WordPress sites are more concerning because the described attack requires no authentication. Confirm plugin presence and exact version before prioritizing remediation.
Exploitation context
ExploitDB is cited as a public exploit reference, so proof-of-concept details are publicly available. The provided data says this CVE is not in KEV, and no cited source claims active exploitation. Treat exploitability as plausible, but do not assume in-the-wild attacks from these sources alone.
Researcher notes
Sources identify Dharma Booking 2.28.3 and earlier, but affected version metadata is sparse and inconsistent. The CVSS vector indicates local attack vector, while the vulnerability description describes unauthenticated parameter manipulation. No official fix is provided in the source bundle, so remediation should be validated against current vendor or WordPress plugin guidance.
Mitigation direction
- Inventory WordPress sites for the Dharma Booking plugin.
- If installed, confirm whether version is 2.28.3 or earlier.
- Disable or remove the plugin if it is not business-critical.
- Check the WordPress plugin page and vendor guidance for fixed versions.
- Restrict access to affected WordPress sites where immediate removal is not possible.
- Review backups and configuration exposure risk for affected sites.
Validation and detection
- Confirm plugin installation through WordPress administration or asset inventory.
- Record the installed Dharma Booking version for each WordPress site.
- Review web logs for suspicious requests to proccess.php and gateway parameters.
- Check whether sensitive configuration files may have been exposed.
- Validate that the plugin is removed, disabled, or updated per vendor guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-98: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2016-20079 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.53.6VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: 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
Base CVSS 3.1 score
6.2MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-39592CVE reference, VulnCheck · exploit
- Official Product HomepageCVE reference, VulnCheck · product
- VulnCheck Advisory: WordPress Dharma Booking 2.28.3 Local File Inclusion via proccess.phpCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.