What is the CVSS score of EUVD-2026-59856?

EUVD-2026-59856 has a CVSS 3.1 base score of 4.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.3%.

Gravity Booster EUVD-2026-59856

| CVE-2026-12477 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-08-16 Wordfence

GHSA-5w9q-5r59-3g9f

WordPress XSS Wordpress Plugin Gravity Booster Styles Layouts For Gravity Forms Wpmonks

4.4

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

4.4 MEDIUM

AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

vuln.today AI

4.0 MEDIUM

AC:H for non-default deployment conditions; PR:H for required editor role; UI:R because a victim must browse the injected page for payload execution.

3.1 AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N

4.0 AV:N/AC:L/AT:P/PR:H/UI:P/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

High

Privileges Required

High

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Aug 16, 2026 - 05:06 vuln.today

CVE Published

Aug 16, 2026 - 04:24 cve.org

MEDIUM 4.4

DescriptionCVE.org

The Gravity Booster - Styles & Layouts for Gravity Forms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 5.26 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

AnalysisAI

Stored Cross-Site Scripting in the Gravity Booster - Styles & Layouts for Gravity Forms WordPress plugin (versions ≤ 5.26) allows authenticated attackers with editor-level permissions to inject persistent malicious scripts into admin settings fields. The injected payload executes in the browser of any user who subsequently visits an affected page, enabling session hijacking, credential theft, or further privilege escalation within the WordPress environment. Exploitation is constrained to multi-site WordPress installations or single-site deployments where the unfiltered_html capability has been explicitly disabled; no public exploit or CISA KEV listing has been identified at time of analysis.

Technical ContextAI

The vulnerability arises from CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically the stored variant where attacker-controlled input is saved to the database and later rendered without adequate escaping. The affected plugin, identified via CPE cpe:2.3:a:wpmonks:gravity_booster_-_styles_&_layouts_for_gravity_forms:*:*:*:*:*:*:*:*, extends Gravity Forms with custom style and layout management. Source references point to three discrete sink locations in the plugin codebase: class-styles.php at lines 76, 147, and 148, and stla-admin-fetch-content-area.php at line 290 - all within admin-facing display and content-area fetch logic where user-supplied style configuration values are echoed back without sanitization or contextual output escaping. The WordPress unfiltered_html capability, when enabled for administrators, normally permits arbitrary HTML; the vulnerability only materializes when this capability is absent (e.g., enforced by multi-site super-admin policy or a security hardening plugin), meaning the plugin incorrectly relies on a capability gate rather than implementing its own output escaping.

RemediationAI

A fix is available via WordPress plugin repository changeset 3637650 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3637650%40styles-and-layouts-for-gravity-forms&new=3637650%40styles-and-layouts-for-gravity-forms); administrators should update to the latest available version above 5.26 through the WordPress plugin dashboard or by downloading the updated package from the WordPress.org plugin repository. A confirmed patched release version number was not independently verifiable from the provided data - verify the installed version post-update exceeds 5.26. If an immediate update is not possible, the primary compensating control is restricting the WordPress editor role: either remove untrusted editor-level accounts, or grant the unfiltered_html capability to editors via a capability management plugin, which eliminates the exploitable condition (note this trade-off relaxes HTML filtering and may introduce other risks). Additionally, a Web Application Firewall rule targeting stored XSS patterns in plugin admin endpoints can reduce risk without altering WordPress role configuration.