CVE-2026-27070
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPEverest Everest Forms Pro allows Stored XSS.This issue affects Everest Forms Pro: from n/a through 1.9.10.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceEverest Forms Pro plugin for WordPress contains a Stored XSS vulnerability where malicious scripts can be injected through form inputs and persisted in the database. When other users view pages displaying the affected form data, the injected scripts execute in their browsers, potentially allowing session hijacking or credential theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Everest Forms Pro plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Everest Forms Pro' in the list. Note the installed version displayed.Affected if Everest Forms Pro plugin is active and installed
-
Check the installed version against the fixed releaseCompare the installed version number to the latest version available from the plugin developer or the WordPress plugin repository release notes.Affected if Installed version lacks the security fix for stored XSS in form inputs
-
Identify forms created with Everest Forms ProIn WordPress admin, go to Everest Forms > All Forms and note all published forms. Check if forms accept user submissions via frontend.Affected if Any published form accepts public submissions without sanitization
-
Inspect form entries for suspicious contentIn WordPress admin, go to Everest Forms > Entries and review stored submissions. Look for script tags, iframe tags, or JavaScript event handlers in form field values.Affected if Any form entry contains unsanitized HTML/JavaScript in input fields
-
Check if form displays are accessible to usersView pages containing Everest Forms shortcodes or form blocks. Inspect page source for rendered field values.Affected if Form data is rendered to users without proper output escaping
A user is affected if Everest Forms Pro is installed, the installed version predates the security fix, and forms with user-submitted data are displayed to other users without output escaping.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Everest Forms Pro to the latest version that addresses this vulnerability, or implement proper input validation and output escaping on all form field handlers and display routines.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27070 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data