Is t3s/content-consent vulnerable?

Composer t3s/content-consent has 1 known advisory in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

1advisories

0critical

0on CISA KEV

0no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2023-50462	Insecure Direct Object Reference in extension "Content Consent" (content_consent)	medium	5.3	`>=2.0.0` and `<2.0.2` or `<1.0.3`	`2.0.2`, `1.0.3`

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.

# one-time install
pip install phpwarden

# then
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

A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.