FULL – Cliente
full-customer · plugin
Known security vulnerabilities for FULL – Cliente. Find out in seconds which version runs on your site with WP Lens.
7 known vulnerabilities
3 exploitable without logging in · latest May 2, 2025
Closed on wordpress.org
Removed from the directory on Sep 13, 2025 · reason: guideline violation. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2023-4243subscriber+≤ 2.2.3
FULL - Customer <= 2.2.3 - Authenticated(Subscriber+) Improper Authorization to Arbitrary Plugin Installation
- High 7.5
CVE-2025-26757unauthenticated · needs a click≤ 3.1.26
WordPress FULL – Cliente plugin <= 3.1.26 - Local File Inclusion vulnerability
- High 7.2
CVE-2024-6447unauthenticated≤ 3.1.12
FULL <= 3.1.12 - Unauthenticated Stored Cross-Site Scripting via License Plan Parameter
- Medium 6.5
CVE-2024-12023subscriber+≤ 3.1.25
FULL – Cliente 3.1.5 - 3.1.25 - Authenticated (Subscriber+) SQL Injection
- Medium 6.5
CVE-2024-54313login required≤ 3.1.25
WordPress FULL – Cliente plugin <= 3.1.25 - Local File Inclusion vulnerability
- Medium 6.1
CVE-2024-9211unauthenticated · needs a click≤ 3.1.22
FULL – Cliente <= 3.1.22 - Reflected Cross-Site Scripting
- Medium 4.3
CVE-2023-4242subscriber+≤ 2.2.3
FULL - Customer <= 2.2.3 - Authenticated(Subscriber+) Information Disclosure via Health Check
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).