WordPress plugin
GigPress 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
- High3
- Medium3
- Low0
All GigPress vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.8 | Authenticated (Subscriber+) SQL Injection ≤2.3.28Update to 2.3.29 | CVE-2023-0381 | |
| High7.2 | SQL Injection <2.3.11Update to 2.3.11 | CVE-2015-9353 | |
| High8.8 | SQL Injection <2.3.9Update to 2.3.9 | CVE-2015-4066 |
- High8.8Authenticated (Subscriber+) SQL Injection
≤2.3.28Update to 2.3.29
- High7.2SQL Injection
<2.3.11Update to 2.3.11
- High8.8SQL Injection
<2.3.9Update to 2.3.9
GigPress: common questions
Does GigPress have known vulnerabilities?
Yes. VulnCrest Radar lists 6 known vulnerabilities in GigPress: 3 high, 3 medium. At least one is not fixed in the latest version.
How do I check which version of GigPress 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 GigPress vulnerability?
CVE-2023-7233, published Jan 19, 2024: GigPress <= 2.3.29 - Authenticated (Admin+) Stored Cross-Site Scripting. Severity: Medium (CVSS 4.4).
Is any GigPress vulnerability listed in CISA KEV?
No. None of the known GigPress vulnerabilities is currently listed in the CISA KEV catalog.