How severe is GHSA-r4r6-j2j3-7pp5?

GHSA-r4r6-j2j3-7pp5 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-r4r6-j2j3-7pp5?

GHSA-r4r6-j2j3-7pp5 affects the following packages: contao/core-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-r4r6-j2j3-7pp5?

Update contao/core-bundle to 4.13.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r4r6-j2j3-7pp5 is resolved across your whole dependency graph.

How do I detect GHSA-r4r6-j2j3-7pp5 in my Packagist dependencies?

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

How do I mitigate GHSA-r4r6-j2j3-7pp5 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 GHSA-r4r6-j2j3-7pp5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r4r6-j2j3-7pp5 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-r4r6-j2j3-7pp5?

GHSA-r4r6-j2j3-7pp5 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th 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-r4r6-j2j3-7pp5?

GHSA-r4r6-j2j3-7pp5 is classified as CWE-384 (CWE-384), CWE-613 (CWE-613). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r4r6-j2j3-7pp5 published, and has it been updated?

GHSA-r4r6-j2j3-7pp5 was published on April 9, 2024 and was last updated on September 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

MEDIUM severity

Contao: Remember-me tokens will not be cleared after a password changeGHSA-r4r6-j2j3-7pp5

MEDIUMFix: contao/contao@3032baa

GHSA-r4r6-j2j3-7pp5 is a medium-severity (CVSS 5.9) CWE-384 vulnerability in contao/core-bundle. A fix is available for contao/core-bundle — see the affected versions and patch details below.

Also known asCVE-2024-30262

Published

Apr 9, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-r4r6-j2j3-7pp5.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.05%

Lower risk than most CVEs46th percentile — riskier than 46% 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

🐘contao/core-bundle

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

When a front end member changes their password, the corresponding remember-me tokens are not removed.

Patches

Update to Contao 4.13.40.

Workarounds

Disable "Allow auto login" in the login module.

References

https://contao.org/en/security-advisories/remember-me-tokens-are-not-cleared-after-a-password-change

For more information

If you have any questions or comments about this advisory, open an issue in contao/contao.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/core-bundle`	all versions	4.13.40`composer require contao/core-bundle:^4.13.40`

Affected Products

1 product · 1 configurations

Application

contaocontao

< 4.13.40

range

Detection & mitigation playbook

Open-source dependency

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

### Impact When a front end member changes their password, the corresponding remember-me tokens are not removed. ### Patches Update to Contao 4.13.40. ### Workarounds Disable "Allow auto login" in the login module. ### References https://contao.org/en/security-advisories/remember-me-tokens-are-not-cleared-after-a-password-change ### For more information If you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).