CVE-2026-3300
Exploitation reported by one source. First attested on 2026-06-05 by GCVE · kevintel.
- Published2026-03-31
- WeaknessCWE-94
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The Everest Forms Pro plugin for WordPress is vulnerable to Remote Code Execution via PHP Code Injection in all versions up to, and including, 1.9.12. This is due to the Calculation Addon's process_filter() function concatenating user-submitted form field values into a PHP code string without proper escaping before passing it to eval(). The sanitize_text_field() function applied to input does not escape single quotes or other PHP code context characters. This makes it possible for unauthenticated attackers to inject and execute arbitrary PHP code on the server by submitting a crafted value in any string-type form field (text, email, URL, select, radio) when a form uses the "Complex Calculation" feature.
Timeline
dates in UTC- 2026-03-3102:15CVE publishedNVD
- 2026-06-0509:20Listed as exploited by GCVEGCVE
- 2026-06-0509:20Exploitation first reportedGCVE
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-3300?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-3300?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-3300 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedHORKimhab/CVE-2026-3300adamshaikhma/CVE-2026-3300 PoC-in-GitHub
Sources
- NVDCVE recordread 2026-10-23
- GCVEexploitation2026-06-05
- CISA-ADPSSVC decisionnone2026-03-31
- OpenCVESSVC decisionnone—
- CNACVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-94read 2026-10-23
- FIRST EPSSEPSS score4.4 %2026-10-22
- PoC-in-GitHubproof of concept2read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-03-31
- Last Modified
- 2026-06-17
- NVD status
- Deferred
Frequently asked questions
What is CVE-2026-3300?
Is CVE-2026-3300 actively exploited?
What is the CVSS score for CVE-2026-3300?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.