CVE
DataPress unauthenticated file read via src parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The DataPress (Dataverse Integration) plugin for WordPress lets an attacker read arbitrary files on the server, remotely and without logging in, through directory traversal in the 'src' parameter. Exploitation requires WP_DEBUG to be enabled on the target site, which is not the default setting.
Original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.9/10CVSS 5.9
- No patch5/5No patch listed yet
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-118519 (DataPress (Dataverse Integration) <= 2.97 - Unauthenticated Arbitrary File Read via 'src' Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-118519 (entry last updated 2026-11-18):
Affected:
- alexacrm DataPress (Dataverse Integration): through 2.97
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-118519 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118519 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c377a0cb-f3a1-498e-8f3e-f6af6f4700f5?source=cve
- https://plugins.trac.wordpress.org/browser/integration-cds/tags/2.97/core.php#L1275
- https://plugins.trac.wordpress.org/browser/integration-cds/tags/2.97/core.php#L1266
- https://plugins.trac.wordpress.org/browser/integration-cds/tags/2.97/core.php#L1283
- https://plugins.trac.wordpress.org/browser/integration-cds/tags/2.97/core.php#L1258
- https://plugins.trac.wordpress.org/changeset/3787286/integration-cds/trunk/core.php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-118519
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-118519"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- alexacrm DataPress (Dataverse Integration)
through 2.97
Evidence 8
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118519
Is CVE-2026-118519 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-118519?
DataPress (Dataverse Integration): through 2.97.Source: cve.now feed data