Skip to main content

Profile Builder EUVDEUVD-2026-102682

| CVE-2026-100186 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-16 Wordfence GHSA-cx8v-98r8-v7fw
7.2
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Access
    Submit registration with scripted First Name
  2. Delivery
    Payload stored unsanitized (Email Confirmation enabled)
  3. Exploit
    Admin/user opens injected confirmation page
  4. Execution
    Script executes in victim browser context
  5. Impact
    Hijack session / act as victim

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the 'Email Confirmation' feature to be enabled in Profile Builder - this is the explicit, named prerequisite from the description and is the primary limiting factor, since sites using default/non-email-confirmation registration flows are not reachable through this path. Given that gate, an unauthenticated remote attacker can inject a stored payload via the First Name field during registration (no authentication or user interaction needed to plant it, consistent with PR:N/UI:N). Execution occurs when a user accesses the injected page (realistically an administrator processing registrations), so impact depends on a privileged user viewing the stored content. Affected versions are all releases up to and including 4.0.3; upgrading past the version fixed in changeset 3741133 removes exposure.

Impact

This is a stored XSS (CWE-79) in the widely-used WordPress Profile Builder plugin, rated CVSS 7.2 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - network-reachable, low-complexity, and unauthenticated (PR:N), with a scope change (S:C) reflecting that injected script executes in a victim's browser context rather than the vulnerable component. The low-but-real confidentiality and integrity impact (C:L/I:L) is typical of XSS: session/cookie theft and limited content manipulation rather than full server compromise. No EPSS score, CISA KEV entry, or public exploit was provided in the input, so per the exploitation-status rules this is 'no public exploit identified at time of analysis.' The single most important mitigating signal - not reflected in the raw 7.2 score - is that exploitation is gated on a non-default plugin setting: the vulnerability is only reachable when the Email Confirmation feature is enabled in Profile Builder. This materially narrows the real-world exposed population below what AV:N/PR:N alone would imply. Net: a credible, vendor-confirmed (Wordfence) vulnerability worth patching promptly on sites that enable Email Confirmation, but not an emergency-grade mass-exploitation threat given no exploitation evidence and the required non-default configuration.

Exploit ScenarioDerived

On a WordPress site running Profile Builder (≤4.0.3) with the Email Confirmation feature enabled, an unauthenticated attacker submits a registration containing a malicious payload in the First Name field, which is stored without sufficient sanitization or output escaping. When a user - typically an administrator reviewing the email-confirmation/registration page - opens the affected page, the script executes in their browser, enabling session hijacking or admin-context actions. No public proof-of-concept was identified in the provided data, but the vendor (Wordfence) has confirmed the flaw and a fix (changeset 3741133).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 16, 2026

Stored cross-site scripting in the WordPress Profile Builder plugin (Cozmoslabs) affects all versions up to and including 4.0.3 and lets unauthenticated remote attackers plant arbitrary JavaScript through the First Name registration field, which executes in the browser of any user who later views the injected page - realistically an administrator processing pending registrations. The attack is explicitly gated on the plugin's Email Confirmation feature being enabled, so sites using default or other registration flows are not reachable through this path. Scoring is CVSS 7.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) with a scope change reflecting script execution in the victim's browser context, and no public exploit has been identified at time of analysis.

RemediationAI

Upgrade the Profile Builder plugin to a release that includes Trac changeset 3741133 (https://plugins.trac.wordpress.org/changeset/3741133/profile-builder), which is the referenced upstream fix; note that the exact patched version number is not confirmed from the available data, so verify against the plugin's changelog before assuming a given release is clean. Upstream fix available (PR/commit); released patched version not independently confirmed. If immediate upgrade is not possible, the most effective compensating control is to disable the plugin's Email Confirmation feature, since the vulnerable code path is only reachable when that feature is enabled - the trade-off is that registrations no longer require email verification, which weakens anti-spam and account-validation controls. A less disruptive alternative is to remove or disable the First Name field from the registration form (or replace it with a plugin-validated custom field) so untrusted values never reach the affected rendering code, at the cost of changing the user-facing registration experience. Organizations can additionally deploy a WAF rule that sanitizes or blocks script/HTML payloads submitted to the registration endpoint and monitor for unexpected script content stored in user profile/First Name data, but WAF filtering is a perimeter measure only and does not remove already-stored payloads - existing suspicious profile entries should be reviewed and cleaned. Full detail is available in the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/f3f2ecdb-bbd0-4834-b731-88724ca0dfd7?source=cve.

Affected VersionsENISA

User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor 0 ≤4.0.3

Affected Packages

euvd user_profile_builder_beautiful_user_registration_forms_user_profiles_user_role_editor no fix

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

The issue is a classic CWE-79 (Improper Neutralization of Input During Web Page Generation) stored/persistent XSS in a WordPress plugin. Profile Builder renders user-supplied profile fields, and the First Name field is not adequately sanitized on input nor escaped on output - the referenced source lines (front-end/default-fields/first-name/first-name.php line 56, and features/email-confirmation/class-email-confirmation.php lines 99-100 plus email-confirmation.php line 470) show where the field value is handled and later emitted during the email-confirmation flow. Because the malicious value is persisted with the user/registration record and re-rendered on subsequent page loads, the payload is stored rather than reflected. The CPE cpe:2.3:a:cozmoslabs:user_profile_builder_-_beautiful_user_registration_forms,_user_profiles_&_user_role_editor confirms the affected vendor package (Cozmoslabs' User Profile Builder). The CVSS vector's S:C (scope change) is appropriate because the injected script executes in a different security context (the victim's browser, potentially an administrator session) than the vulnerable component, and PR:N/UI:N confirm the payload can be planted without authentication or victim interaction - interaction is required only at execution time, when a user opens the injected page.

Know when User Profile Builder Beautiful User Registration Forms User Profiles User Role Editor 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 (Wordfence) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 7.2 HIGH

Unauthenticated remote injection (AV:N/PR:N/UI:N) with browser-context execution crossing a security boundary (S:C) and limited C/I typical of XSS; the Email Confirmation prerequisite is a deployment gate, not attacker-facing complexity, so AC:L is retained.

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

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

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

DescriptionCVE.org

The User Profile Builder - Beautiful User Registration Forms, User Profiles & User Role Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via First Name Field in all versions up to, and including, 4.0.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only exploitable when the Email Confirmation feature is enabled in Profile Builder.

Executive ViewAI

Why It Matters

The Profile Builder plugin for WordPress (Cozmoslabs), versions up to and including 4.0.3, carries a stored cross-site scripting flaw that allows an unauthenticated visitor to plant malicious script in the First Name field of a registration, which then runs in the browser of whoever later reviews that record - typically an administrator approving pending sign-ups. Any organization running this plugin with the Email Confirmation feature enabled should treat the affected WordPress administrator accounts as potentially reachable and prioritize remediation, since a compromised admin session can translate into full control of the site and its hosted content. There is currently no vendor-released patch, so leadership should expect a period of manual risk management rather than a single update fix.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable the plugin's Email Confirmation feature where operationally feasible (this removes the described attack path); restrict or disable open self-registration; deploy WAF or server-side input validation that strips HTML/script content from registration fields such as First Name; require administrators to review pending registrations in a clean session; and monitor vendor advisories for a fixed release.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Medium
popular WordPress user-registration plugin, but exploit path needs non-default feature
Social Media
1
Sightings
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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

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

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

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