WordPress plugin
ProcessingJS for WordPress security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All ProcessingJS for WordPress vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting ≤1.2.2No patch available | CVE-2025-6039 |
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤1.2.2No patch available
ProcessingJS for WordPress: common questions
Does ProcessingJS for WordPress have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in ProcessingJS for WordPress: 1 medium. At least one is not fixed in the latest version.
How do I check which version of ProcessingJS for WordPress I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent ProcessingJS for WordPress vulnerability?
CVE-2025-6039, published Jul 3, 2025: ProcessingJS for WordPress <= 1.2.2 - Authenticated (Contributor+) Stored Cross-Site Scripting. Severity: Medium (CVSS 6.4).
Is any ProcessingJS for WordPress vulnerability listed in CISA KEV?
No. None of the known ProcessingJS for WordPress vulnerabilities is currently listed in the CISA KEV catalog.