How severe is GHSA-j72f-h752-mx4w?

GHSA-j72f-h752-mx4w has a CVSS score of 5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-j72f-h752-mx4w?

GHSA-j72f-h752-mx4w affects the following packages: codeigniter4/shield (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-j72f-h752-mx4w?

Update codeigniter4/shield to 1.0.0-beta.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j72f-h752-mx4w is resolved across your whole dependency graph.

How do I detect GHSA-j72f-h752-mx4w in my Packagist dependencies?

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

How do I mitigate GHSA-j72f-h752-mx4w 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-j72f-h752-mx4w actively exploited in the wild?

No public exploit code has been indexed for GHSA-j72f-h752-mx4w 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-j72f-h752-mx4w?

GHSA-j72f-h752-mx4w has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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 GHSA-j72f-h752-mx4w?

GHSA-j72f-h752-mx4w is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j72f-h752-mx4w published, and has it been updated?

GHSA-j72f-h752-mx4w was published on November 23, 2023 and was last updated on February 16, 2024. 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

MEDIUM severity

Insertion of Sensitive Information into LogGHSA-j72f-h752-mx4w

MEDIUMFix: codeigniter4/shield@7e84c3f

GHSA-j72f-h752-mx4w is a medium-severity (CVSS 5) CWE-532 vulnerability in codeigniter4/shield. A fix is available for codeigniter4/shield — see the affected versions and patch details below.

Also known asCVE-2023-48708

Published

Nov 23, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘codeigniter4/shield

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

If successful login attempts are recorded, the raw tokens are stored in the log table. If a malicious person somehow views the data in the log table, he or she can obtain a raw token, which can then be used to send a request with that user's authority.

When you (1) use the following authentiactors,

AccessTokens (tokens)
JWT (jwt)
HmacSha256 (hmac)

and you (2) log successful login attempts, the raw tokens are stored.

Patches

Upgrade to Shield v1.0.0-beta.8 or later.

Workarounds

Disable logging for successful login attempts by the configuration files.

AccessTokens or HmacSha256
- Set Config\AuthToken::$recordLoginAttempt to Auth::RECORD_LOGIN_ATTEMPT_FAILURE or Auth::RECORD_LOGIN_ATTEMPT_NONE
JWT
- Set Config\AuthJWT::$recordLoginAttempt to Auth::RECORD_LOGIN_ATTEMPT_FAILURE or Auth::RECORD_LOGIN_ATTEMPT_NONE

References

https://codeigniter4.github.io/shield/getting_started/authenticators/

For more information

If you have any questions or comments about this advisory:

Open an issue or discussion in codeigniter4/shield
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`codeigniter4/shield`	all versions	1.0.0-beta.8`composer require codeigniter4/shield:^1.0.0-beta.8`

Affected Products

1 product · 7 configurations

Application

shieldcodeigniter

1 version

1.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for codeigniter4/shield, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update codeigniter4/shield to 1.0.0-beta.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j72f-h752-mx4w 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

### Impact If successful login attempts are recorded, the raw tokens are stored in the log table. If a malicious person somehow views the data in the log table, he or she can obtain a raw token, which can then be used to send a request with that user's authority. When you (1) **use the following authentiactors**, - [AccessTokens](https://codeigniter4.github.io/shield/references/authentication/tokens/) (`tokens`) - [JWT](https://codeigniter4.github.io/shield/addons/jwt/) (`jwt`) - [HmacSha256](https://codeigniter4.github.io/shield/references/authentication/hmac/) (`hmac`) and you (2) **log su