Vulnerability · CVE-2023-39345
Unauthorized Access to Private Fields in User Registration API
Published Nov 3, 2023 · catalog updated Jun 17, 2026 · Unauthorized Access to Private
Last checked Nov 4, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2023-39345. EPSS is 0.59%. Act only if a listed version of Unauthorized Access to Private is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Unauthorized Access to Private).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-57997 · Medium
- CVE-2026-27886 · Critical
- CVE-2026-22707 · Medium
- CVE-2025-64526 · Medium
- CVE-2026-22706 · Low
- Severity
- High7.6
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.59%
- Remediation
- Version ranges on file
- Affected products
- cpe strapi/strapi · npm @strapi/plugin-users-permissions · npm @strapi/strapi
### System Details | Name | Value | |----------|------------------------| | OS | Windows 11 | | Version | 4.11.1 (node v16.14.2) | | Database | mysql | ### Description I marked some fields as private fields in user content-type, and tried to register as a new user via api, at the same time I added content to fill the private fields and sent a post request, and as you can see from the images below, I can write to the private fields.     To prevent this, I went to the extension area and tried to extend the register method, for this I wanted to do it using the sanitizeInput function that I know in the source codes of the strap. But the sanitizeInput function did not filter out private fields. here's the solution I've temporarily kept to myself, code snippet
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe strapi/strapi< 4.13.1
- npm @strapi/plugin-users-permissions4.0.0
- npm @strapi/strapi4.0.0
How to fix CVE-2023-39345
Upgrade
CVE-2023-39345 lists a fix boundary at 4.13.1. Compare the installed build with that boundary before you change production.
Version check
Affected < 4.13.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2023-39345. EPSS is 0.59%. Act only if a listed version of Unauthorized Access to Private is installed.
Which versions are affected?
Compare what you have installed with < 4.13.1, 4.0.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-287: Improper Authentication. EPSS 0.59%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Nov 3, 2023 · Maintainer security tabs
Detected
### System Details | Name | Value | |----------|------------------------| | OS | Windows 11 | | Version | 4.11.1 (node v16.14.2) | | Database | mysql | ### Description I marked some fields as private fields in user content-type, and tried to register as a new user via api, at the same time I added content to fill the private fields and sent a post request, and as you can see from the images below,
Nov 3, 2023 · Maintainer security tabs
Updated
### System Details | Name | Value | |----------|------------------------| | OS | Windows 11 | | Version | 4.11.1 (node v16.14.2) | | Database | mysql | ### Description I marked some fields as private fields in user content-type, and tried to register as a new user via api, at the same time I added content to fill the private fields and sent a post request, and as you can see from the images below,
Jun 17, 2026 · Monitored products — high
Updated
strapi is an open-source headless CMS. Versions prior to 4.13.1 did not properly restrict write access to fielded marked as private in the user registration endpoint. As such malicious users may be able to errantly modify their user records. This issue has been addressed in version 4.13.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Sources
- CVE.orgVulnerability recordCVE-2023-39345
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2023-39345
30-day exploitation probability 0.59%
first.org - Maintainer security tabsVendor advisoryGHSA-gc7p-j5xm-xxh2
### System Details | Name | Value | |----------|------------------------| | OS | Windows 11 | | Version | 4.11.1 (node v16.14.2) | | Database | mysql | ### Description I marked some fields as private fields in user content-type, and tried to register as a new user via api, at the same time I added content to fill the private fields and sent a post request, and as you can see from the images below,
github.com - Monitored products — highVendor advisoryCVE-2023-39345
strapi is an open-source headless CMS. Versions prior to 4.13.1 did not properly restrict write access to fielded marked as private in the user registration endpoint. As such malicious users may be able to errantly modify their user records. This issue has been addressed in version 4.13.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 4, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 4, 2026
- Monitored products — highNov 4, 2026
- CVE.orgNov 2, 2026
- Maintainer security tabsNov 1, 2026