WordPress plugin
Convert Classic Editor to Gutenberg Blocks 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 Convert Classic Editor to Gutenberg Blocks vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Reflected Cross-Site Scripting via fs_request_get ≤1.9.2No patch available | CVE-2023-33999 |
- Medium6.1Reflected Cross-Site Scripting via fs_request_get
≤1.9.2No patch available
Convert Classic Editor to Gutenberg Blocks: common questions
Does Convert Classic Editor to Gutenberg Blocks have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Convert Classic Editor to Gutenberg Blocks: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Convert Classic Editor to Gutenberg Blocks 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 Convert Classic Editor to Gutenberg Blocks vulnerability?
CVE-2023-33999, published Jul 18, 2023: Freemius SDK <= 2.5.9 - Reflected Cross-Site Scripting via fs_request_get. Severity: Medium (CVSS 6.1).
Is any Convert Classic Editor to Gutenberg Blocks vulnerability listed in CISA KEV?
No. None of the known Convert Classic Editor to Gutenberg Blocks vulnerabilities is currently listed in the CISA KEV catalog.