CVE-2026-3512 MEDIUM

CVE-2026-3512: Writeprint Stylometry <= 0.1 - Reflected Cross-Site Scripting via 'p' Parameter

Vendor Alhadeff
Product Writeprint Stylometry
Weakness CWE-79 · XSS
Published March 18, 2026
Last update April 8, 2026

CVSS base score

6.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

The Writeprint Stylometry plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'p' GET parameter in all versions up to and including 0.1. This is due to insufficient input sanitization and output escaping in the bjl_wprintstylo_comments_nav() function. The function directly outputs the $_GET['p'] parameter into an HTML href attribute without any escaping. This makes it possible for authenticated attackers with Contributor-level permissions or higher to inject arbitrary web scripts in pages that execute if they can successfully trick another user into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

Writeprint Stylometry versions 0.1 and earlier contain a cross-site scripting (XSS) vulnerability. An attacker can inject malicious scripts that execute in a victim's browser when they visit an affected page. The vulnerability requires user interaction and can affect other users or the site itself depending on where the injection occurs.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in a victim's browser and steal data or perform actions on their behalf.

Potential impact on your site

04Site Impact

Visitors' browsers can be compromised; attackers may steal session tokens, credentials, or perform unauthorized actions.

Conditions required to exploit

05Prerequisites

Victim must visit a page containing the attacker's malicious input; no authentication required.

Key dates

06Disclosure timeline

March 18, 2026 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE