dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-32142

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Shopware is an open commerce platform. /api/_info/config route exposes information about licenses. This vulnerability is fixed in 7.8.1 and 6.10.15.

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

Shopware's /api/_info/config endpoint exposes sensitive license information to users without proper authentication or authorization. This information disclosure vulnerability has a CVSS 5.3 (Medium) severity rating.

MitigationUpgrade Shopware to version 7.8.1 or 6.10.15 to patch the vulnerability. As a temporary measure, restrict access to the /api/_info/config route via web server configuration or firewall rules until the upgrade can be performed.

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

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Shopware installation and version
    Check your Shopware installation by looking for shopware.yml, composer.json, or the Shopware admin panel. In the admin panel, go to Configuration > Basic Information or check the Shopware version via the shopware version command if you have CLI access.
    Affected if The installed version is Shopware 6.x before 6.10.15 or Shopware 7.x before 7.8.1
  2. Verify the /api/_info/config endpoint is accessible
    Send a GET request to https://yourdomain.com/api/_info/config using curl or a browser. No authentication should be required.
    Affected if The endpoint returns a response with HTTP status 200 and contains license-related information such as license keys, shop ID, or enterprise features.
  3. Inspect response for sensitive license data
    Examine the JSON response from the /api/_info/config endpoint. Look for fields containing license keys, shop identifiers, or feature flags related to commercial Shopware editions.
    Affected if The response includes fields like license, shopId, or other license-related configuration data that should not be publicly accessible.
  4. Check web server access logs
    Review your web server access logs (Apache, Nginx) for requests to /api/_info/config from unauthenticated IP addresses.
    Affected if The logs show successful 200 responses to this endpoint from users who did not authenticate.

You are affected if your Shopware version is below 6.10.15 or 7.8.1 and the /api/_info/config endpoint returns license-sensitive information without authentication.

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 Shopware to version 7.8.1 or 6.10.15 to patch the vulnerability. As a temporary measure, restrict access to the /api/_info/config route via web server configuration or firewall rules until the upgrade can be performed.

Recommended fix High confidence

Shopware 6.10.15 or later for 6.x branch; Shopware 7.8.1 or later for 7.x branch

  1. 1. Identify your current Shopware installation version by checking the shopware.php file or composer.json
  2. 2. If running Shopware 6.x, upgrade to version 6.10.15 or later
  3. 3. If running Shopware 7.x, upgrade to version 7.8.1 or later
  4. 4. Before upgrading, backup your database and files
  5. 5. Review Shopware's upgrade documentation for your specific version path
  6. 6. Run the database migration after upgrading
  7. 7. Verify the /api/_info/config route no longer exposes license information
  8. 8. Test critical commerce functions post-upgrade
Caveat Review Shopware 6.10 and 7.8 release notes for potential breaking changes specific to your plugins and theme customizations

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA1.0 h
12.0 hours of engineering $2,110
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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