dbcve.org
Apps GraphqlApplication · Vtex

CVE-2023-28877

HIGH · 7.5 CVSS v3.1 Published 2023-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 VTEX [email protected] GraphQL API module does not properly restrict unauthorized access to private configuration data. ([email protected] is unaffected by this issue.)

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 · moderate confidence

The VTEX [email protected] module contains a broken access control vulnerability in its GraphQL API where authorization checks are not properly enforced on certain resolvers. This allows unauthenticated or unauthorized attackers to query sensitive private configuration data through GraphQL introspection and queries.

MitigationUpgrade to [email protected] which contains the fixed authorization logic, or apply any vendor-supplied patches to enforce proper access controls on all GraphQL endpoints.

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
Apps GraphqlApplication
Affected:= 2.x

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify apps-graphql module version
    Locate the apps-graphql dependency in your VTEX app's manifest.json or package.json file, or run a platform-specific command to list installed app versions (e.g., vtex list or examining the node_modules/apps-graphql/package.json)
    Affected if The installed version is exactly 2.x (any 2.x release)
  2. Verify GraphQL API is exposed
    Access your VTEX environment's GraphQL endpoint (typically at /graphql or /_v/private/graphql) using a tool like curl or a browser, sending a basic GraphQL query without providing authentication headers
    Affected if The endpoint returns a valid GraphQL response without requiring authentication credentials
  3. Check if GraphQL introspection is enabled
    Send an introspection query (the standard __schema or __type queries) to the exposed GraphQL endpoint without authentication, or inspect the GraphQL playground/IDE settings
    Affected if Introspection queries return the full schema including private resolvers and types without authentication
  4. Test for unauthorized sensitive data access
    Execute known GraphQL queries that target private configuration resolvers (such as queries for appSettings, adminConfigs, or payment credentials) against the endpoint without valid authorization tokens
    Affected if The queries return sensitive configuration data or private information without proper access controls

Your environment is affected if apps-graphql version 2.x is installed AND the GraphQL API is externally accessible without authentication enforcing proper authorization checks on sensitive resolvers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to [email protected] which contains the fixed authorization logic, or apply any vendor-supplied patches to enforce proper access controls on all GraphQL endpoints.

Recommended fix Moderate confidence

[email protected] (any stable 3.x release)

  1. Identify all VTEX apps using [email protected] dependency in your project
  2. Update the apps-graphql dependency in your package.json or manifest.json from 2.x to version 3.x or latest stable 3.x release
  3. Run dependency resolution to ensure the upgrade is compatible with other dependencies
  4. Test the GraphQL API endpoints to verify private configuration data is now properly protected
  5. Deploy the updated application
Caveat Review the apps-graphql changelog for any breaking changes between v2 and v3; testing is recommended to ensure API compatibility

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

Fix this in Apps Graphql Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28877 — 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-28877 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