The Everest Forms plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.4.4. This is due to the load_previous_field_value() method in class-evf-form-task.php accepting arbitrary URL values from $_POST data for upload fields without domain restriction, which are then passed to wp_remote_head() in the get_local_file_size() method of class-evf-form-fields-upload.php. This makes it possible for unauthenticated attackers to force the WordPress server to make outbound HTTP HEAD requests to arbitrary URLs by submitting a form with an upload field containing a malicious URL while leaving a required field empty to trigger form re-rendering.
CVE-2026-5096
Score 5.3 from GitHub Security Advisory published 2026-08-28. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
References (4)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/everest-forms/trunk/includes/abstracts/class-evf-form-fields-upload.php#L1196
- security@wordfencehttps://plugins.trac.wordpress.org/browser/everest-forms/trunk/includes/class-evf-form-task.php#L1448
- security@wordfencehttps://plugins.trac.wordpress.org/changeset/3507814/
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/c5bbf7ed-c154-4153-adbf-59f0f7aa3a18?source=cve
Vendor Advisories for CVE-2026-5096(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:54 UTCGHSA enrichment
- 2026-08-28 20:29 UTCGHSA enrichment
- 2026-08-28 18:42 UTCEG score recompute
- 2026-08-28 18:42 UTCGHSA enrichment
- 2026-08-28 16:34 UTCEG score recompute
- 2026-08-28 15:30 UTCEG score recompute
- 2026-08-28 15:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p91CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-5096?
When was CVE-2026-5096 disclosed?
Is CVE-2026-5096 actively exploited?
What is the CVSS score of CVE-2026-5096?
How do I remediate CVE-2026-5096?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-5096
Is Your Infrastructure Affected by CVE-2026-5096?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.