How severe is GHSA-f339-246p-wwjp?

No CVSS score has been assigned to GHSA-f339-246p-wwjp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f339-246p-wwjp?

GHSA-f339-246p-wwjp affects the following packages: frosh/adminer-platform (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-f339-246p-wwjp?

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

How do I detect GHSA-f339-246p-wwjp 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 GHSA-f339-246p-wwjp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-f339-246p-wwjp actively exploited in the wild?

No public exploit code has been indexed for GHSA-f339-246p-wwjp 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 GHSA-f339-246p-wwjp?

GHSA-f339-246p-wwjp has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th 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.

When was GHSA-f339-246p-wwjp published, and has it been updated?

GHSA-f339-246p-wwjp was published on February 10, 2026 and was last updated on February 10, 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

GHSA-f339-246p-wwjp — frosh/adminer-platform

Fix: FriendsOfShopware/FroshPlatformAdminer@c4dd6c3

GHSA-f339-246p-wwjp is a security 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 asCVE-2026-25878

Published

Feb 10, 2026

Updated

Feb 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, 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 GHSA-f339-246p-wwjp.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% 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`

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 GHSA-f339-246p-wwjp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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 GHSA-f339-246p-wwjp in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works