Skip to main content

HappyForms CVE-2026-14556

| EUVDEUVD-2026-107147 MEDIUM
Improper Encoding or Escaping of Output (CWE-116)
2026-10-21 WPScan GHSA-qwq5-hm76-r6p9
5.4
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach public HappyForms form
  2. Delivery
    Submit form with malicious HTML in referral value
  3. Exploit
    Unescaped value embedded in notification email
  4. Execution
    Admin opens notification email
  5. Impact
    Injected HTML renders / phishing payload shown

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding for downstream
Exploitation Conditions

Exploitation requires that the target site runs HappyForms before 1.26.15 with at least one publicly reachable form that generates admin notification emails (the plugin's default email-notification feature), and that the referral value is passed through to that email unescaped. The decisive limiting factor is user interaction (UI:R): the injected HTML only takes effect when a site administrator actually opens and views the notification email, so there is no automatic server-side compromise. No attacker authentication is needed (PR:N), and no special non-default plugin configuration is indicated by the description beyond the standard notification-email functionality being enabled.

Impact

This is a genuine but moderate-severity issue, not a top-tier emergency. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N, base 5.4) shows a network-reachable, low-complexity flaw requiring no attacker privileges - consistent with the description's 'unauthenticated attackers' claim. The key risk-limiting signal is UI:R: exploitation is not self-contained because a site administrator must open and view the attacker-influenced notification email for the injected HTML to render. A public exploit exists (reported by WPScan), which raises the practical likelihood of opportunistic abuse, but POC availability is NOT the same as active exploitation. No EPSS score was provided, so exploitation probability cannot be quantified. The CVE is NOT listed in CISA KEV and there is no SSVC decision data in the input, so there is no evidence of confirmed in-the-wild exploitation. The realistic impact is bounded: HTML injection into admin-facing emails enables phishing, content spoofing, and social-engineering of administrators rather than direct code execution or data theft, which matches the Low confidentiality/integrity and None availability sub-scores. Overall: treat as a standard-priority patching item for affected HappyForms installs, elevated slightly by public POC and no-authentication reachability, but not a drop-everything critical.

Exploit ScenarioDerived

An unauthenticated attacker submits a HappyForms form while supplying a crafted referral value containing malicious HTML (e.g., a fake login link or spoofed support notice). Because the referral value is embedded unescaped into the form-notification email, the injected markup renders when a site administrator opens that email, enabling phishing or content spoofing. A public exploit for this technique is already available via WPScan, and the low attack complexity (AC:L) means crafting the request is trivial.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

HTML injection in the HappyForms WordPress plugin (versions before 1.26.15) allows unauthenticated attackers to place arbitrary HTML into the notification emails that site administrators receive, because a user-controlled referral value is embedded without sanitisation or escaping. The injected markup only renders when an administrator actually opens the notification email, so exploitation requires user interaction and yields limited integrity impact on the email content rather than server-side compromise. Publicly available exploit code exists per the WPScan disclosure; there is no CISA KEV indication of active exploitation, and the severity is moderate.

RemediationAI

Upgrade HappyForms to version 1.26.15 or later, which is the first release that sanitises and escapes the referral value before it is embedded in notification emails; this is the only complete fix and should be applied to every site running an older build. Where an immediate update is not possible, reduce exposure by disabling admin notification emails for publicly reachable forms (the plugin's notification setting), accepting the operational cost of losing submission alerts, or by restricting forms behind membership/authentication so untrusted visitors cannot supply a referral value at all - both are partial mitigations that depend on the site's submission volume and access model rather than removing the flaw. Because injected markup executes only in the recipient's mail client, treating notification emails from pre-1.26.15 sites as untrusted (plain-text rendering or HTML blocking) limits the practical effect of the injection but does not remediate the plugin. Verify the applied version and consult the vendor advisory at https://wpscan.com/vulnerability/7673862c-b37c-4c7e-af3f-c32cbd2deb23/ for confirmation details.

Affected VersionsENISA

Happyforms 0 <1.26.15

Affected Packages

euvd happyforms fix: 1.26.15

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

HappyForms is a WordPress form-builder plugin that sends email notifications to site administrators when submissions arrive. The referral value - a user-controllable field associated with a form submission - is concatenated into the notification email body without output encoding, so an unauthenticated visitor can supply markup that the mail client later interprets. The root-cause class is improper neutralisation of user-controlled input during generation of a downstream document (the CWE-79/CWE-116 family), although no CWE identifier was assigned in the source data. The supplied CPE (cpe:2.3:a:unknown:happyforms) is vendor-unnormalised, so version pinning must rely on the WPScan advisory rather than CPE matching. Impact is bounded by the email rendering path: the injected content lives in the mail body, not in a server-executed context, which is consistent with the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N - network reachable and unauthenticated (PR:N), but contingent on the administrator opening the message (UI:R) and limited to integrity effects within the notification email.

Know when Happyforms gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 5.4 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
vuln.today AI 4.3 MEDIUM

Network-reachable unauthenticated form submission (AV:N/PR:N/AC:L), but impact is limited HTML injection realized only when an admin reads the email (UI:R), affecting integrity (I:L) with no confidentiality or availability loss.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

2
Patch available
Oct 21, 2026 - 10:16 EUVD
CVE Published
Oct 21, 2026 - 08:38 cve.org
MEDIUM 5.4

DescriptionCVE.org

The HappyForms WordPress plugin before 1.26.15 does not sanitise or escape a user-controlled referral value before embedding it in the form notification email, allowing unauthenticated attackers to inject arbitrary HTML into the emails site administrators receive.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Medium
popular but non-ubiquitous third-party WordPress form plugin
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy