CVE-2026-118519 json
DataPress (Dataverse Integration) <= 2.97 - Unauthenticated Arbitrary File Read via 'src' Parameter
published 15h ago modified 11h ago also EUVD-2026-128564
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
The DataPress (Dataverse Integration) plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.97 via the 'src' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires WP_DEBUG to be defined as true on the target site — not the default on production, but commonly enabled on staging, development, and misconfigured production environments.
Is CVE-2026-118519 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- alexacrm DataPress (Dataverse Integration)
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/c377a0cb-f3a1-498e-8f3e-f6af6f4700f5?source=cve
- plugins.trac.wordpress.org /browser/integration-cds/tags/2.97/core.php#L1275
- plugins.trac.wordpress.org /browser/integration-cds/tags/2.97/core.php#L1266
- plugins.trac.wordpress.org /browser/integration-cds/tags/2.97/core.php#L1283
- plugins.trac.wordpress.org /browser/integration-cds/tags/2.97/core.php#L1258
- plugins.trac.wordpress.org /changeset/3787286/integration-cds/trunk/core.php
Sources
- CVE List CVE-2026-118519
- NVD CVE-2026-118519
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.