Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2008-3261: Open Redirect in Claroline redirector.php (pre-1.8.10)

Published Jul 22, 2008 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS4.8%92nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Claroline
IdentifiersCVE-2008-3261CWE-601

An open redirect vulnerability exists in Claroline before version 1.8.10, specifically in claroline/redirector.php. The vulnerability is due to insufficient validation of the 'url' parameter, allowing remote attackers to redirect users to arbitrary external websites. This can be exploited to facilitate phishing attacks or social engineering by tricking users into visiting malicious sites under the guise of a trusted Claroline domain.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows attackers to redirect users to attacker-controlled sites, enabling phishing, credential theft, or further exploitation. The vulnerability undermines user trust in the application and can be leveraged in social engineering campaigns.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, implement input validation or sanitization on the 'url' parameter in claroline/redirector.php to ensure only trusted, internal URLs are allowed. Additionally, consider disabling the redirector functionality until a patch can be applied.

Remediation

Patch, then assume compromise.

Upgrade Claroline to version 1.8.10 or later, where the input validation for the 'url' parameter in redirector.php has been corrected to prevent open redirects.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ClarolineClarolineapplication
FAQ

Frequently asked questions

Is CVE-2008-3261 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-3261 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-3261?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2008-3261.
Is there a patch for CVE-2008-3261?
Upgrade Claroline to version 1.8.10 or later, where the input validation for the 'url' parameter in redirector.php has been corrected to prevent open redirects.
What products are affected by CVE-2008-3261?
Claroline.
How severe is CVE-2008-3261?
CVE-2008-3261 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 4.8% (92nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.