FroshAdminer Adminer UI is accessible without admin session

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-25878: 0.41% estimated exploitation activity in the next 30 days; percentile 35.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Unauthenticated access to Adminer UI Details The Adminer route (/admin/adminer) was accessible without Shopware admin authentication. The route was configured with authrequired=false and performed no session validation, exposing the Adminer UI to unauthenticated users. Note: Database access itself requires credentials that are only set through the ACL-protected API endpoint. Direct database access without prior admin login is not possible through this vulnerability alone. Impact An unauthenticated user could access the Adminer interface, potentially disclosing version information or exploiting Adminer-specific vulnerabilities. Patches Version 2.2.1 adds session validation. The Adminer route now verifies an authenticated session flag before rendering — returning HTTP 403 otherwise. Workarounds Deactivate or uninstall the plugin.

Published by the source

10 Feb 2026, 00:22 UTC

Last modified by the source

10 Feb 2026, 00:22 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f339-246p-wwjp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25878

Advisory: FroshAdminer Adminer UI is accessible without admin session
IDs: CVE-2026-25878, GHSA-f339-246p-wwjp
Record: https://patchnext.com/advisories/cve-2026-25878 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: frosh/adminer-platform 2.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist frosh/adminer-platform: affected < 2.2.1; fixed in 2.2.1

## Suggested inspection (read-only)
- Packagist frosh/adminer-platform: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on frosh/adminer-platform.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f339-246p-wwjp (GitHub-reviewed advisory GHSA-f339-246p-wwjp lists affected ranges: Packagist frosh/adminer-platform >=0 <2.2.1)

Commands are suggestions: review each one before running it.