dbcve.org
Full CustomerWordPress extension · Full

CVE-2023-4243

HIGH · 8.8 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to after 2.2.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The FULL - Customer plugin for WordPress is vulnerable to Arbitrary File Upload via the /install-plugin REST route in versions up to, and including, 2.2.3 due to improper authorization. This allows authenticated attackers with subscriber-level permissions and above to execute code by installing plugins from arbitrary remote locations including non-repository sources onto the site, granted they are packaged as a valid WordPress plugin.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FULL - Customer plugin for WordPress has an improper authorization vulnerability in its /install-plugin REST route. The endpoint fails to properly validate user capabilities, allowing any authenticated user with subscriber-level permissions or higher to trigger plugin installations from arbitrary remote URLs. Since the plugin accepts non-WordPress-repository packages formatted as valid WordPress plugins, attackers can achieve remote code execution.

MitigationUpdate to version 2.2.4 or later which should implement proper capability checks (install_plugins capability). Until patched, consider disabling the plugin or restricting REST API access via wp-config.php filters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Full CustomerWordPress extension
Affected:<= 2.2.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Full Customer plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'Full Customer' or inspect the plugin directory at wp-content/plugins/ for a folder named 'full-customer' or similar
    Affected if The Full Customer plugin appears in the installed plugins list
  2. Check installed plugin version
    In WordPress admin, click on the Full Customer plugin to view its details and note the version number, or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if The displayed version number is 2.2.3 or lower
  3. Verify REST API endpoint exists
    Send an authenticated GET request to /wp-json/full-customer/v1/install-plugin or /wp-json/ustomer/v1/install-plugin (check actual route structure) using a tool like curl with valid subscriber-level credentials
    Affected if The endpoint responds and accepts requests from users with subscriber-level permissions (any authenticated user)
  4. Test endpoint authorization bypass
    Using a low-privileged account (subscriber role), attempt to send a POST request to the install-plugin endpoint with a malicious plugin URL to see if installation proceeds without install_plugins capability check
    Affected if The endpoint allows plugin installation without verifying the user has install_plugins capability

A user is affected if the Full Customer plugin version is 2.2.3 or lower AND the /install-plugin REST endpoint is accessible to authenticated users with subscriber-level permissions or higher.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.2.3
Interim mitigation

Update to version 2.2.4 or later which should implement proper capability checks (install_plugins capability). Until patched, consider disabling the plugin or restricting REST API access via wp-config.php filters.

Recommended fix Moderate confidence

Latest version of FULL - Customer plugin (version higher than 2.2.3)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'FULL - Customer' plugin
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from the WordPress plugin repository and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Full Customer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4243 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4243 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data