Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2009-4363: Text_Filter/lib/Horde/Text/Filter/Xss.php in Horde Application Framework before 3.3.6, Horde Groupware before 1.2.5, and Horde Groupware Web

Noroxi assessment

Priority: Monitor (action score 17/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.8% of all records.
  • Fixed version: horde3 (Debian:4.0) 3.1.3-4etch7; horde3 (Debian:5.0) 3.2.2+debian0-2+lenny2.

Low priority for now. Upgrade to horde3 (Debian:4.0) 3.1.3-4etch7; horde3 (Debian:5.0) 3.2.2+debian0-2+lenny2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Text_Filter/lib/Horde/Text/Filter/Xss.php in Horde Application Framework before 3.3.6, Horde Groupware before 1.2.5, and Horde Groupware Webmail Edition before 1.2.5 does not properly handle data: URIs, which allows remote attackers to conduct cross-site scripting (XSS) attacks via data:text/html values for the HREF attribute of an A element in an HTML e-mail message. NOTE: the vendor states that the issue is caused by "an XSS vulnerability in Firefox browsers."

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Dec 21, 2009
Updated
Jun 16, 2026
EPSS
1.3% · 71th percentile

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2009-4363

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
hordeapplication framework
hordegroupware

Limit the impact of XSS

This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.

Check security headers

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • horde application frameworkup to 3.3.5 inclusive
  • horde application framework2.0
  • horde application framework2.1
  • horde application framework2.1.3
  • horde application framework2.2
  • horde application framework2.2.1
  • horde application framework2.2.3
  • horde application framework2.2.4
  • horde application framework2.2.4_rc1
  • horde application framework2.2.5
  • horde application framework2.2.6
  • horde application framework3.0
  • horde application framework3.0.1
  • horde application framework3.0.2
  • horde application framework3.0.3
  • horde application framework3.0.4
  • horde application framework3.0.6
  • horde application framework3.0.7
  • horde application framework3.0.8
  • horde application framework3.0.9

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:4.0horde3before 3.1.3-4etch73.1.3-4etch7
Debian:5.0horde3before 3.2.2+debian0-2+lenny23.2.2+debian0-2+lenny2

Other highest-scoring records for the same primary product.

  • CVE-2006-1491Eval injection vulnerability in Horde Application Framework versions 3.0 before 3.0.10 and 3.1 before 3.1.1 allows remote attackers to execu
    42Plan
  • CVE-2009-3701Multiple cross-site scripting (XSS) vulnerabilities in the administration interface in Horde Application Framework before 3.3.6, Horde Group
    18Monitor
  • CVE-2009-3236The form library in Horde Application Framework 3.2 before 3.2.5 and 3.3 before 3.3.5; Groupware 1.1 before 1.1.6 and 1.2 before 1.2.4; and
    18Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2005-0961May 2, 2005 · Cross-site scripting (XSS) vulnerability in Horde 3.0.4 before 3.0.4-RC2 allows remote attackers to inject arbitrary web script or HTML via
    17Monitor
  • ← EarlierCVE-2006-4256Aug 21, 2006 · index.php in Horde Application Framework before 3.1.2 allows remote attackers to include web pages from other sites, which could be useful f
    18Monitor
  • ← EarlierCVE-2008-5917Jan 20, 2009 · Cross-site scripting (XSS) vulnerability in the XSS filter (framework/Text_Filter/Filter/xss.php) in Horde Application Framework 3.2.2 and 3
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:horde33.1.3-4etch7 · Debian:4.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    P
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:N/I:P/A:N

    nvd-primary

    Root cause

    User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    commentEl.innerHTML = comment.body;

    Fixed

    ts
    commentEl.textContent = comment.body;

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records