CVE-2024-29885: Silverstripe Reports are still accessible even when `canView()` returns false

medium Affects silverstripe/reports. Feed 2026.10.29.1, updated 2026-10-28; published 2024-07-17; advisory modified 2026-09-10.

Silverstripe Reports are still accessible even when `canView()` returns false

Package: silverstripe/reports Composer
Affected versions: <5.2.3
Fixed in: 5.2.3
Severity: medium CVSS 4.3
Exploitation: not on CISA KEV · EPSS 0% (34.5th percentile)
Published: 2024-07-17
Source: osv.dev

References

CWE-200 CWE-863

NVD record silverstripe/reports advisories

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs How findings are ranked

Related advisories

CVE-2017-5487 medium wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php in the REST API implemen same weakness: CWE-200
CVE-2018-7251 critical Anchor CMS Logs Credentials same weakness: CWE-200
CVE-2021-39327 medium The BulletProof Security WordPress plugin is vulnerable to sensitive information disclosur same weakness: CWE-200
CVE-2009-0815 medium TYPO3 leaks a hash secret in an error message same weakness: CWE-200
CVE-2014-2383 medium DOMPDF Arbitrary File Read same weakness: CWE-200
CVE-2019-17671 medium In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because same weakness: CWE-200