How severe is CVE-2026-25878?

No CVSS score has been assigned to CVE-2026-25878 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-25878?

CVE-2026-25878 affects the following packages: frosh/adminer-platform (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-25878?

Update frosh/adminer-platform to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25878 is resolved across your whole dependency graph.

How do I detect CVE-2026-25878 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for frosh/adminer-platform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-25878 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-25878 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-25878 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-25878?

CVE-2026-25878 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-25878?

CVE-2026-25878 is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-25878 published, and has it been updated?

CVE-2026-25878 was published on February 9, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-25878 — adminer-platform

Fix: FriendsOfShopware/FroshPlatformAdminer@c4dd6c3

CVE-2026-25878 is a Missing Authentication vulnerability in frosh/adminer-platform. A fix is available for frosh/adminer-platform — see the affected versions and patch details below.

FroshAdminer Adminer UI is accessible without admin session

Also known asGHSA-f339-246p-wwjp

Published

Feb 9, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25878.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘frosh/adminer-platform

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Unauthenticated access to Adminer UI

Details

The Adminer route (/admin/adminer) was accessible without Shopware admin authentication. The route was configured with auth_required=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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`frosh/adminer-platform`	all versions	2.2.1`composer require frosh/adminer-platform:^2.2.1`

Affected Products

1 product · 1 configurations

Application

froshadminerfriendsofshopware

< 2.2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for frosh/adminer-platform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update frosh/adminer-platform to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25878 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Summary Unauthenticated access to Adminer UI ### Details The Adminer route (/admin/adminer) was accessible without Shopware admin authentication. The route was configured with auth_required=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 i

O3 Security · Impact-Aware SCA

Is CVE-2026-25878 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works