WordPress plugin
WP Custom field for Gutenberg Editor 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 WP Custom field for Gutenberg Editor 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
WP Custom field for Gutenberg Editor: common questions
Does WP Custom field for Gutenberg Editor have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in WP Custom field for Gutenberg Editor: 1 medium. At least one is not fixed in the latest version.
How do I check which version of WP Custom field for Gutenberg Editor 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 WP Custom field for Gutenberg Editor 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 WP Custom field for Gutenberg Editor vulnerability listed in CISA KEV?
No. None of the known WP Custom field for Gutenberg Editor vulnerabilities is currently listed in the CISA KEV catalog.