CVE-2026-3512
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Writeprint Stylometry WordPress plugin contains a reflected XSS vulnerability in the bjl_wprintstylo_comments_nav() function. The 'p' GET parameter is directly output into an HTML href attribute without sanitization or escaping, allowing authenticated attackers with Contributor-level or higher permissions to inject arbitrary JavaScript via crafted URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Writeprint Stylometry plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'writeprint-stylometry', 'writeprint', or similar. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if the plugin is listed.Affected if The plugin folder or database entry exists and the plugin is active.
-
Locate the vulnerable function bjl_wprintstylo_comments_nav()Search plugin PHP files for the function definition 'function bjl_wprintstylo_comments_nav()'. Check all .php files in the plugin directory.Affected if The function is found in the plugin files.
-
Inspect how the 'p' parameter is handled in the vulnerable functionOpen the file containing bjl_wprintstylo_comments_nav(). Look for $_GET['p'] or $_REQUEST['p'] being used. Check if it is directly output into an HTML href attribute without esc_attr(), esc_html(), or similar escaping functions.Affected if The code shows $_GET['p'] being concatenated into an href attribute without sanitization.
-
Verify the attack vector is reachableTest accessing a page that calls bjl_wprintstylo_comments_nav() with a crafted URL parameter like ?p=test". Inspect the generated HTML source to confirm the parameter value appears unescaped in an href attribute.Affected if The 'p' parameter value appears verbatim (unescaped) in the HTML output within an href attribute.
The environment is affected if the Writeprint Stylometry plugin is installed with the vulnerable bjl_wprintstylo_comments_nav() function present and the 'p' GET parameter is being output without escaping in an href attribute.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply proper output escaping (such as esc_attr()) to the 'p' parameter before rendering in the href attribute, or update to a patched version when available from the plugin vendor.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3512 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data