Plugins · customer-area · data as of 2026-11-04
Is WP Customer Area safe? Known vulnerabilities and latest version
- Latest version
- 8.4.4
- Last updated
- 2026-11-03
- Active installs
- 10,000+
- Known issues on record
- 13
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.2+
WP Customer Area is a modular all-in-one solution to manage private content with WordPress. — by Aguila Technologies
What to do
- Update to the latest version (8.4.4). Anything older than 8.4.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get customer-area --field=version shows what you run; wp plugin update customer-area updates it.
Check your version
Known vulnerabilities
13 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.5 CVE-2026-116854 · published 2026-10-30
Cross-site scripting (XSS) in WP Customer Area (8.4.0 and older)
- Affected
- 8.4.0 and older
- Fixed in
- 8.4.1
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Subscriber Cross Site Scripting (XSS) in WP Customer Area <= 8.4.0 versions.
medium 6.4 CVE-2026-7640 · published 2026-07-14
Stored cross-site scripting (XSS) in WP Customer Area (8.3.5 and older)
- Affected
- 8.3.5 and older
- Fixed in
- 8.3.6 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The WP Customer Area plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'type' attribute of the `customer-area-protected-content` shortcode in all versions up to, and including, 8.3.5. This is due to insufficient input sanitization and output escaping on the shortcode attribute. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
NVD CVE-2026-7640Wordfence advisorywordpress.orgPlugin source
high 8.8 CVE-2026-42661 · published 2026-06-15
Path traversal / file read in WP Customer Area (8.3.4 and older)
- Affected
- 8.3.4 and older
- Fixed in
- 8.3.5
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Custom role Path Traversal in WP Customer Area <= 8.3.4 versions.
high 8.8 CVE-2026-3464 · published 2026-04-17
Remote code execution in WP Customer Area (8.3.4 and older)
- Affected
- 8.3.4 and older
- Fixed in
- 8.3.5 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The WP Customer Area plugin for WordPress is vulnerable to arbitrary file read and deletion due to insufficient file path validation in the 'ajax_attach_file' function in all versions up to, and including, 8.3.4. This makes it possible for authenticated attackers with a role that an administrator grants access to (e.g., Subscriber) to to read the contents of arbitrary files on the server, which can contain sensitive information, or delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
NVD CVE-2026-3464Wordfence advisoryCode change (fix)Plugin source
high 7.5 CVE-2025-60201 · published 2025-11-06
File inclusion in WP Customer Area (older than 8.3.4)
- Affected
- older than 8.3.4
- Fixed in
- 8.3.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in aguilatechnologies WP Customer Area customer-area allows PHP Local File Inclusion. This issue affects WP Customer Area: before 8.3.4.
medium 4.3 CVE-2025-49982 · published 2025-06-20
Missing authorization check in WP Customer Area (8.3.4 and older)
- Affected
- 8.3.4 and older
- Fixed in
- 8.3.5 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in aguilatechnologies WP Customer Area customer-area allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Customer Area: from n/a through <= 8.3.4.
medium 4.3 CVE-2024-12436 · published 2025-01-27
Cross-site request forgery (CSRF) in WP Customer Area (8.2.4 and older)
- Affected
- 8.2.4 and older
- Fixed in
- 8.2.5 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The WP Customer Area WordPress plugin through 8.2.4 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks
medium 4.3 CVE-2024-12280 · published 2025-01-27
Cross-site request forgery (CSRF) in WP Customer Area (8.2.4 and older)
- Affected
- 8.2.4 and older
- Fixed in
- 8.2.5 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The WP Customer Area WordPress plugin through 8.2.4 does not have CSRF check in place when deleting its logs, which could allow attackers to make a logged in to delete them via a CSRF attack
medium 6.1 CVE-2024-0665 · published 2024-01-24
Reflected cross-site scripting (XSS) in WP Customer Area (8.2.2 and older)
- Affected
- 8.2.2 and older
- Fixed in
- 8.2.3 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The WP Customer Area plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'tab' parameter in all versions up to, and including, 8.2.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
medium 4.3 CVE-2023-6741 · published 2024-01-16
Security issue in WP Customer Area (older than 8.2.1)
- Affected
- older than 8.2.1
- Fixed in
- 8.2.1
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The WP Customer Area WordPress plugin before 8.2.1 does not properly validate users capabilities in some of its AJAX actions, allowing malicious users to edit other users' account address.
medium 6.5 CVE-2023-6824 · published 2024-01-16
Missing authorization check in WP Customer Area (older than 8.2.1)
- Affected
- older than 8.2.1
- Fixed in
- 8.2.1
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The WP Customer Area WordPress plugin before 8.2.1 does not properly validates user capabilities in some of its AJAX actions, allowing any users to retrieve other user's account address.
high 7.1 CVE-2022-4745 · published 2023-02-13
Cross-site request forgery (CSRF) in WP Customer Area (older than 8.1.4)
- Affected
- older than 8.1.4
- Fixed in
- 8.1.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The WP Customer Area WordPress plugin before 8.1.4 does not have CSRF checks when performing some actions such as chmod, mkdir and copy, which could allow attackers to make a logged-in admin perform them and create arbitrary folders, copy file for example.
medium 6.1 CVE-2017-18519 · published 2019-08-20
Cross-site scripting (XSS) in WP Customer Area (older than 7.4.3)
- Affected
- older than 7.4.3
- Fixed in
- 7.4.3
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- advisory text · score by NVD
Details from the advisory
The customer-area plugin before 7.4.3 for WordPress has XSS via admin pages.
Recent activity
- 2026-11-03 — latest release on wordpress.org (8.4.4).
- 2026-10-30 — Cross-site scripting (XSS) disclosed (CVE-2026-116854), fixed in 8.4.1.
- 2026-07-14 — Stored cross-site scripting (XSS) disclosed (CVE-2026-7640), fixed in 8.3.6.
- 2026-06-15 — Path traversal / file read disclosed (CVE-2026-42661), fixed in 8.3.5.
Get an email when WP Customer Area has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for WP Customer Area (customer-area) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (4) · Cross-site request forgery (CSRF) (3) · Missing authorization (2) · Path traversal and file read (1) · Remote code execution (1) · File inclusion (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/customer-area (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/customer-area"><img src="https://laskyr.com/plugins/customer-area/badge.svg" alt="WP Customer Area vulnerability status"></a>