CVE-2026-111978: The GiveWP WordPress plugin before 4.19.0.1 does not properly validate a user-supplied filename before readin

Q: How do I fix CVE-2026-111978?

givewp: upgrade to 4.19.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-111978 being exploited?

CVE-2026-111978 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-111978 affect?

CVE-2026-111978 affects givewp. Severity is high (CVSS n/a). The GiveWP WordPress plugin before 4.19.0.1 does not properly validate a user-supplied filename before reading it from disk, allowing users with a high-privilege custom role to perform path traversal, disclose the contents of JSON-parseabl

Q: How urgent is CVE-2026-111978?

Priority 1/100. No elevated risk signals yet.

Routine

HIGH n/aUPGRADE

CVE-2026-111978 is a high-severity flaw (CVSS n/a) affecting givewp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The GiveWP WordPress plugin before 4.19.0.1 does not properly validate a user-supplied filename before reading it from disk, allowing users with a high-privilege custom role to perform path traversal, disclose the contents of JSON-parseable files anywhere on the server, and overwrite the GiveWP WordPress plugin before 4.19.0.1's stored configuration.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	n/a (High)
EPSS exploit chance	0.2% (top 95%)
CISA exploited list	No
Published	2026-10-25
Last modified	2026-10-25

Publisher (CNA): WPScan · Vendor: unknown · Source: CVE Program record (NVD analysis pending)

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-10-25 06:00 UTCPublished CVE record published
2026-10-25 06:00 UTCUpdated Record last modified

unknown givewp UPGRADE

Affected: < 4.19.0.1

Fixed in: 4.19.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy givewp || rpm -q givewp || givewp --version

2. UPGRADE to 4.19.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade givewp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade givewp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-111978?

givewp: upgrade to 4.19.0.1. Exact commands for each OS are on this page.

Is CVE-2026-111978 being exploited?

CVE-2026-111978 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-111978 affect?

CVE-2026-111978 affects givewp. Severity is high (CVSS n/a). The GiveWP WordPress plugin before 4.19.0.1 does not properly validate a user-supplied filename before reading it from disk, allowing users with a high-privilege custom role to perform path traversal, disclose the contents of JSON-parseabl

How urgent is CVE-2026-111978?

Priority 1/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2026-111981 HIGH n/a UPGRADE The GiveWP WordPress plugin before 4.19.0.1 does not perform a capability check when handling donor address c
CVE-2026-111980 HIGH n/a UPGRADE The GiveWP WordPress plugin before 4.19.0.1 does not correctly determine which page a page-capability request
CVE-2026-111979 HIGH n/a UPGRADE The GiveWP WordPress plugin before 4.19.0.1 does not properly sanitise and escape one of its donation form te
CVE-2026-111976 HIGH n/a UPGRADE The GiveWP WordPress plugin before 4.19.0.1 does not perform any status or capability check when rendering a

References

← Back to latest CVEs