phpCAS is an authentication library that allows PHP applications to easily authenticate users via a Central Authentication Service (CAS) server. The phpCAS library uses HTTP headers to determine the service URL used to validate tickets. This allows an attacker to control the host header and use a valid ticket granted for any authorized service in the same SSO realm (CAS server) to authenticate to the service protected by phpCAS. Depending on the settings of the CAS server service registry in worst case this may be any other service URL (if the allowed URLs are configured to "^(https)://.*") or may be strictly limited to known and authorized services in the same SSO federation if proper URL service validation is applied. This vulnerability may allow an attacker to gain access to a victim's account on a vulnerable CASified service without victim's knowledge, when the victim visits attacker's website while being logged in to the same CAS server. phpCAS 1.6.0 is a major version upgrade that starts enforcing service URL discovery validation, because there is unfortunately no 100% safe default config to use in PHP. Starting this version, it is required to pass in an additional service base URL argument when constructing the client class. For more information, please refer to the upgrading doc. This vulnerability only impacts the CAS client that the phpCAS library protects against. The problematic service URL discovery behavior in phpCAS < 1.6.0 will only be disabled, and thus you are not impacted from it, if the phpCAS configuration has the following setup: 1. phpCAS::setUrl() is called (a reminder that you have to pass in the full URL of the current page, rather than your service base URL), and 2. phpCAS::setCallbackURL() is called, only when the proxy mode is enabled. 3. If your PHP's HTTP header input X-Forwarded-Host, X-Forwarded-Server, Host, X-Forwarded-Proto, X-Forwarded-Protocol is sanitized before reaching PHP (by a reverse proxy, for example), you will not be impacted by this vulnerability either. If your CAS server service registry is configured to only allow known and trusted service URLs the severity of the vulnerability is reduced substantially in its severity since an attacker must be in control of another authorized service. Otherwise, you should upgrade the library to get the safe service discovery behavior.
CVE-2022-39369
“—” beside the score: it is equal to NVD's CVSS score.
Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2022-11-01. NVD baseline CVSS 8.0; sources differ by 0.0.
Also known asEUVD-2022-7285 (ENISA EUVD) · GHSA-8q72-6qq8-xv64 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.0
- EG Score
- 8.0HIGHmedium confidence
- EG Risk
- 37EG Risk 37/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity80% × 45%Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation2.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 2.4%
- EPSS %ILE
- 84th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 2.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 1, 2022
Last Modified
November 21, 2024
Advisory Details (5)
Auto-updated Sep 21, 2026[SECURITY] Fedora 35 Update: php-pear-CAS-1.6.0-1.fc35 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VJZGTWJ5ZXUUT47EHARNOUUNTH6SYDSE/[SECURITY] Fedora 36 Update: php-pear-CAS-1.6.0-1.fc36 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RUA2JM6YT3ZXSZLBJVRA32AXYM3GJMO3/[SECURITY] Fedora 37 Update: php-pear-CAS-1.6.0-1.fc37 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2XL7SMW6ESSP2Y6HHRYWW2MMCZSI4LBZ/[SECURITY] [DLA 3485-1] php-cas security update
https://lists.debian.org/debian-lts-announce/2023/07/msg00007.htmlService Hostname Discovery Exploitation · Advisory · apereo/phpCAS · GitHub
https://github.com/apereo/phpCAS/security/advisories/GHSA-8q72-6qq8-xv64Patch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | php-cas (1.3.8-1ubuntu0.22.04.1) @ jammy | 2026-10-21 | ubuntu |
| ubuntu | ocsinventory-server (2.8.1+dfsg1-1ubuntu0.1) @ jammy | 2026-10-21 | ubuntu |
| ubuntu | php-cas (1.3.3-2ubuntu1+esm1) @ xenial | 2026-10-21 | ubuntu |
| composer | apereo/phpcas @ 1.6.0 (fixes < 1.6.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(6 across 6 ecosystems)
Debian:10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| php-cas | 1.3.6-1 |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| php-cas | 1.3.8-1 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| php-cas | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| php-cas | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| php-cas | — |
| — |
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apereo/phpcas | 1.3.3 ... 1.5.0 (9 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(3)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 10× in last 7d / 40× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 96 of 217 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:38 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-11-01 16:30 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-11-01 08:24 UTCGHSA enrichmentGHSA-8q72-6qq8-xv64 · GitHub severity HIGH · GitHub CVSS 8.0
- 2026-11-01 08:24 UTCEG score recompute
- 2026-10-31 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-30 16:30 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-29 16:29 UTCEPSS rescoreEPSS 2.4% · 84th percentile
- 2026-10-28 16:28 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-28 00:42 UTCEG score recompute
- 2026-10-27 16:28 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-26 16:28 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-25 18:01 UTCEG score recompute
- 2026-10-25 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-24 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-21 06:23 UTCEG score recompute
- 2026-10-21 06:23 UTCVendor advisory
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-18 08:28 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-16 16:35 UTCEPSS rescoreEPSS 2.0% · 80th percentile
Show 71 moreShow fewer
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-15 13:24 UTCOSV refresh
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-12 18:48 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-11 23:12 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 2.0% · 79th percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 2.0% · 79th percentile
- 2026-10-04 23:19 UTCEPSS rescoreEPSS 2.0% · 79th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-10-01 19:47 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-30 16:03 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-24 07:18 UTCOSV refresh
- 2026-09-22 14:45 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-20 20:13 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-17 19:24 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-15 03:07 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 1.2% · 66th percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-05 00:29 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.2% · 65th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.1% · 63rd percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-18 11:02 UTCOSV refresh
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
- 2026-08-11 13:39 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-10 14:08 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 1.1% · 61st percentile
- 2026-08-03 06:57 UTCOSV refresh
Related CVEs(same product + same CWE)
Same product
4 shownDebian:11:php-cas · Packagist:apereo/phpcas
Same CWE
10 shownCWE-99 · CWE-1287
Frequently asked(5)
What is CVE-2022-39369?
When was the CVE record for CVE-2022-39369 published?
Is CVE-2022-39369 actively exploited?
What is the CVSS score of CVE-2022-39369?
How do I remediate CVE-2022-39369?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-39369
Is Your Infrastructure Affected by CVE-2022-39369?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.