FULL – Cliente vulnerabilities
Plugin slug full-customer · 6 known vulnerabilities · latest disclosed 2025-05-01 · WordPress.org page
Every listed vulnerability has a fix. Version 3.1.26 or later is not affected by any of them. If your site runs an older version, update it.
3 of 6 rated high or critical (CVSS 7 or more).
Known vulnerabilities in FULL – Cliente
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 6.5 | <= 3.1.25 | 3.1.26 | CVE-2024-12023 | 2025-05-01 | Advisory |
| High 8.8 | <= 3.1.25 | 3.1.26 | CVE-2024-54313 | 2024-12-11 | Advisory |
| Medium 6.1 | <= 3.1.22 | 3.1.23 | CVE-2024-9211 | 2024-10-10 | Advisory |
| High 7.2 | <= 3.1.12 | 3.1.13 | CVE-2024-6447 | 2024-07-10 | Advisory |
| High 8.8 | <= 2.2.3 | 2.3 | CVE-2023-4243 | 2023-08-08 | Advisory |
| Medium 4.3 | <= 2.2.3 | 2.3 | CVE-2023-4242 | 2023-08-08 | Advisory |
Check if a site is affected
Enter a site address to see which version of FULL – Cliente and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the FULL – Cliente plugin safe to use?
All 6 known issues are fixed in current versions (3.1.26 or later). Keeping it updated is what matters.
How do I check which version of FULL – Cliente 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.