ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-34093

Making all attributes on a content-type public via review workflows

Published Jul 25, 2023 · catalog updated Apr 11, 2025 · Making all attributes on

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-34093. EPSS is 0.71%. Act only if a listed version of Making all attributes on is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Making all attributes on).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.71%
Remediation
Version ranges on file
Affected products
cpe strapi/strapi · npm @strapi/database · npm @strapi/strapi · npm @strapi/utils

### Summary Anyone (Strapi developers, users, plugins) can make every attribute of a Content-Type public without knowing it. ### Details When dealing with content-types inside a Strapi instance, we can extend those using the appropriate container: The vulnerability only affects the handling of content types by Strapi, not the actual content types themselves. Users can use plugins or modify their own content types without realizing that the getter is being removed, which can result in any attribute becoming public. This can lead to sensitive information being exposed or the entire system being taken control of by an attacker(having access to password hashes). ### PoC Extend any content type on runtime (like in the bootstrap functions) and do a copy of the content-type object. This will have as effect to remove the getter and as we rely on it in sanitization, every attributes will be considered as public. ### Impact Everyone can be impacted. Depending on how people are using/extending content-types. If the users are mutating the content-type, they will not be affected.

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.10.8
  • npm @strapi/database<= 4.10.6
  • npm @strapi/strapi<= 4.10.6
  • npm @strapi/utils<= 4.10.6

How to fix CVE-2023-34093

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-34093. EPSS is 0.71%. Act only if a listed version of Making all attributes on is installed.

Which versions are affected?

Compare what you have installed with < 4.10.8, <= 4.10.6. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-200: Exposure of Sensitive Information. EPSS 0.71%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Strapi security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 25, 2023 · Maintainer security tabs

    Detected

    ### Summary Anyone (Strapi developers, users, plugins) can make every attribute of a Content-Type public without knowing it. ### Details When dealing with content-types inside a Strapi instance, we can extend those using the appropriate container: The vulnerability only affects the handling of content types by Strapi, not the actual content types themselves. Users can use plugins or modify their o

  2. Apr 11, 2025 · Maintainer security tabs

    Updated

    ### Summary Anyone (Strapi developers, users, plugins) can make every attribute of a Content-Type public without knowing it. ### Details When dealing with content-types inside a Strapi instance, we can extend those using the appropriate container: The vulnerability only affects the handling of content types by Strapi, not the actual content types themselves. Users can use plugins or modify their o

Sources

  • CVE.orgVulnerability recordCVE-2023-34093

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2023-34093

    30-day exploitation probability 0.71%

    first.org
  • Maintainer security tabsVendor advisoryGHSA-chmr-rg2f-9jmf

    ### Summary Anyone (Strapi developers, users, plugins) can make every attribute of a Content-Type public without knowing it. ### Details When dealing with content-types inside a Strapi instance, we can extend those using the appropriate container: The vulnerability only affects the handling of content types by Strapi, not the actual content types themselves. Users can use plugins or modify their o

    github.com
  • Monitored products — highVendor advisoryCVE-2023-34093

    Strapi is an open-source headless content management system. Prior to version 4.10.8, anyone (Strapi developers, users, plugins) can make every attribute of a Content-Type public without knowing it. The vulnerability only affects the handling of content types by Strapi, not the actual content types themselves. Users can use plugins or modify their own content types without realizing that the gette

    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