How severe is CVE-2008-3227?

No CVSS score has been assigned to CVE-2008-3227 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2008-3227?

CVE-2008-3227 affects the following packages: joomla/framework (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2008-3227?

Update joomla/framework to 1.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2008-3227 is resolved across your whole dependency graph.

How do I detect CVE-2008-3227 in my Packagist dependencies?

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

How do I mitigate CVE-2008-3227 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2008-3227 actively exploited in the wild?

No public exploit code has been indexed for CVE-2008-3227 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 CVE-2008-3227?

CVE-2008-3227 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 67th 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 CVE-2008-3227?

CVE-2008-3227 is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2008-3227 published, and has it been updated?

CVE-2008-3227 was published on May 1, 2022 and was last updated on December 5, 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

CVE-2008-3227 — framework

CVE-2008-3227 is a CWE-59 vulnerability in joomla/framework. A fix is available for joomla/framework — see the affected versions and patch details below.

Joomla! Open Redirect vulnerability

Published

May 1, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘joomla/framework

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

Unspecified vulnerability in Joomla! before 1.5.4 has unknown impact and attack vectors related to a "User Redirect Spam fix," possibly an open redirect vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`joomla/framework`	all versions	1.5.4`composer require joomla/framework:^1.5.4`

Affected Products

1 product · 24 configurations

Application

joomlajoomla

≤ 1.5.3

23 versions

1.01.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.10

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for joomla/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update joomla/framework to 1.5.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2008-3227 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

Unspecified vulnerability in Joomla! before 1.5.4 has unknown impact and attack vectors related to a "User Redirect Spam fix," possibly an open redirect vulnerability.

O3 Security · Impact-Aware SCA

Is CVE-2008-3227 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works