GigPress vulnerabilities
Plugin slug gigpress · 6 known vulnerabilities · latest disclosed 2024-01-19 · WordPress.org page
1 vulnerability has no fixed version yet. If you use this plugin, consider disabling or replacing it until a fix is released.
3 of 6 rated high or critical (CVSS 7 or more).
Known vulnerabilities in GigPress
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 4.4 | <= 2.3.29 | No fix yet | CVE-2023-7233 | 2024-01-19 | Advisory |
| High 8.8 | <= 2.3.28 | 2.3.29 | CVE-2023-0381 | 2023-02-06 | Advisory |
| Medium 6.4 | <= 2.3.27 | 2.3.28 | CVE-2022-4759 | 2023-01-04 | Advisory |
| High 7.2 | < 2.3.11 | 2.3.11 | CVE-2015-9353 | 2015-08-24 | Advisory |
| Medium 6.1 | <= 2.3.10 | 2.3.11 | CVE-2015-9354 | 2015-08-24 | Advisory |
| High 8.8 | < 2.3.9 | 2.3.9 | CVE-2015-4066 | 2015-05-26 | Advisory |
Check if a site is affected
Enter a site address to see which version of GigPress and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the GigPress plugin safe to use?
1 known issue(s) have no fix yet, so check the table above before using it.
How do I check which version of GigPress my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.