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

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

Ultimate Post EUVD-2026-42520

| CVE-2026-13253 MEDIUM

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

2026-07-09 Wordfence

GHSA-fmqh-3qcq-wcxg

WordPress XSS Wordpress Plugin Post Grid Gutenberg Blocks Postx Wpxpo

6.4

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

6.4 MEDIUM

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

vuln.today AI

5.4 MEDIUM

UI:R applied because victim must visit the injected page; all other metrics match provided vector; PR:L reflects mandatory contributor authentication.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 09, 2026 - 08:42 vuln.today

CVE Published

Jul 09, 2026 - 06:52 nvd

MEDIUM 6.4

DescriptionCVE.org

The Ultimate Post plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'moreResultsText' block attribute of the ultimate-post/advanced-search block in versions up to and including 5.0.31. This is due to insufficient input sanitization and output escaping in the Advanced_Search::content() render callback: the attribute value is filtered with wp_kses(), which strips disallowed HTML tags but does NOT escape HTML special characters such as double quotes in plain text, and the result is then concatenated directly into the data-viewmoretext HTML attribute without esc_attr(). This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AnalysisAI

Stored Cross-Site Scripting in the Ultimate Post (PostX) WordPress plugin versions up to and including 5.0.31 allows authenticated contributors to permanently inject arbitrary JavaScript into WordPress pages via the 'moreResultsText' attribute of the advanced-search Gutenberg block. The root cause is a sanitization gap: the render callback applies wp_kses() which strips disallowed HTML tags but does not encode special characters like double quotes in attribute context, and the unsanitized value is then concatenated directly into the data-viewmoretext HTML attribute without esc_attr(), allowing attribute boundary escape. No public exploit code has been identified at time of analysis, and no EPSS data was provided, but the contributor-level access requirement represents the primary real-world friction point for exploitation.

Technical ContextAI

The vulnerability resides in the Advanced_Search::content() render callback of the 'ultimate-post' WordPress plugin (CPE: cpe:2.3:a:wpxpo:post_grid_gutenberg_blocks_-_postx:*:*:*:*:*:*:*:*), marketed under both the 'Ultimate Post' and 'PostX' branding. The block editor exposes a 'moreResultsText' block attribute that is passed through wp_kses(), a WordPress function designed to strip disallowed HTML tags. However, wp_kses() is not an attribute-context encoder - it does not escape double quotes or other HTML special characters in text that will appear inside an HTML attribute value. The vulnerable code, visible in the WordPress.org trac browser for versions 5.0.27 and 5.0.28 at blocks/Advanced_Search.php line 116 and line 108, concatenates this insufficiently sanitized value directly into the data-viewmoretext HTML attribute without wrapping it through esc_attr(). This is a classic CWE-79 (Improper Neutralization of Input During Web Page Generation) sink: context mismatch between the sanitization function (HTML body context) and the output destination (HTML attribute context). The stored nature means the payload persists in the post content and fires for every subsequent visitor.

RemediationAI

A fix has been committed upstream as WordPress.org plugin changeset 3598669 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3598669%40ultimate-post&new=3598669%40ultimate-post); however, the exact patched release version is not independently confirmed from available data - site administrators should update to the latest available version of the Ultimate Post / PostX plugin beyond 5.0.31 and verify via the WordPress admin plugin page. The correct code-level fix is to wrap the moreResultsText attribute value through esc_attr() before concatenation into the data-viewmoretext HTML attribute, replacing reliance on wp_kses() alone for attribute-context output. As a compensating control where updating immediately is not possible, administrators should audit and restrict contributor-level user roles, removing or demoting untrusted contributor accounts, since contributor access is the hard prerequisite for exploitation. Restricting the use of the advanced-search block to trusted editors via block permissions (e.g., through a roles capability plugin) is a viable interim mitigation with minimal editorial workflow impact.