How severe is GHSA-vfpx-q664-h93m?

GHSA-vfpx-q664-h93m has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vfpx-q664-h93m?

GHSA-vfpx-q664-h93m affects the following packages: auth0/wordpress (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-vfpx-q664-h93m?

Update auth0/wordpress to 5.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vfpx-q664-h93m is resolved across your whole dependency graph.

How do I detect GHSA-vfpx-q664-h93m in my Packagist dependencies?

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

How do I mitigate GHSA-vfpx-q664-h93m 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.

How does O3 Security protect against GHSA-vfpx-q664-h93m?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vfpx-q664-h93m can be triaged on real exposure rather than presence alone.

Is GHSA-vfpx-q664-h93m actively exploited in the wild?

No public exploit code has been indexed for GHSA-vfpx-q664-h93m 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.

When was GHSA-vfpx-q664-h93m published, and has it been updated?

GHSA-vfpx-q664-h93m was published on April 3, 2026 and was last updated on April 3, 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

HIGH severity

GHSA-vfpx-q664-h93m — auth0/wordpress

HIGH

GHSA-vfpx-q664-h93m is a high-severity (CVSS 8.2) vulnerability in auth0/wordpress. A fix is available for auth0/wordpress — see the affected versions and patch details below.

Auth0 WordPress Plugin has Insufficient Entropy in Cookie Encryption

Published

Apr 3, 2026

Updated

Apr 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 3, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘auth0/wordpress

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

Impact

In applications built with the Auth0 PHP SDK, cookies are encrypted with insufficient entropy, which may result in threat actors brute-forcing the encryption key and forging session cookies.

Am I Affected?

Consumers are affected if their application meets the following preconditions:

It is using the Auth0 WordPress Plugin, versions between 5.0.0-BETA0 and 5.5.0
Auth0 WordPress plugin using the Auth0-PHP SDK versions between 8.0.0 to 8.18.0.

Resolution

Upgrade Auth0/wordpress to version 5.6.0 or greater.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`auth0/wordpress`	≥ 5.0.0-BETA0&&< 5.6.0	5.6.0`composer require auth0/wordpress:^5.6.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for auth0/wordpress, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update auth0/wordpress to 5.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vfpx-q664-h93m 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vfpx-q664-h93m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vfpx-q664-h93m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact In applications built with the Auth0 PHP SDK, cookies are encrypted with insufficient entropy, which may result in threat actors brute-forcing the encryption key and forging session cookies. ### Am I Affected? Consumers are affected if their application meets the following preconditions: - It is using the Auth0 WordPress Plugin, versions between 5.0.0-BETA0 and 5.5.0 - Auth0 WordPress plugin using the Auth0-PHP SDK versions between 8.0.0 to 8.18.0. ### Resolution Upgrade Auth0/wordpress to version 5.6.0 or greater.

O3 Security · Impact-Aware SCA

Is GHSA-vfpx-q664-h93m in your dependencies?

O3 Security finds GHSA-vfpx-q664-h93m across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works