jwp-a11y

jwp-a11y has one disclosed vulnerability in the WordSec catalog, all reported in 2024; it remains unpatched as of September 2026. Their average CVSS score is 4.4, and the most serious one scores 4.4 out of 10.

The most common weakness is Cross-Site Scripting, behind 1 of the records (100%).

The one issue recorded for jwp-a11y has no published fix yet, which makes virtual patching the only reliable mitigation. The oldest unresolved one dates back to 2024.

All of these findings were reported by Taufique Noorani. jwp-a11y is installed on roughly 100 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 7.1.

Strategic Overview

Avg CVSSMedium
4.4/ 10
Patch Coverage0%
Open

1

Fixed

0

Get automatic notifications for all jwp-a11y vulnerabilities before they are exploited.

Most severe open issueCVSS 4.4CVE-2024-11190

jwp-a11y <= 4.1.7 - Authenticated (Administrator+) Stored Cross-Site Scripting

Read the full analysis

Vulnerability Records

1 records
Plugin Profile
Latestv5.3.4
5.0(1)
100/100
Last Updated
2026-08-22 (22d ago)
Active Installs
100+
Downloads
10,145
Requires WP
6.0+
Requires PHP
8.3+
Tested up to
WP 7.1
Created
2016-12-16 (10y ago)

jwp-a11y checks the accessibility of WordPress post content while you edit and save posts. It helps editors notice accessibility issues earlier in the writing workflow and keeps legacy public result pages available through the existing [jwp_a11y_results] shortcode. This version focuses on three practical tasks: checking post content with jidaikobo/a11yc while editing, showing previously saved public result pages through [jwp_a11y_results], providing reading material for understanding accessibility criteria through the admin tools page and [jwp_a11y_doc]. translate by using GlotPress

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C