Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2009-3633: Cross-site scripting (XSS) vulnerability in the t3lib_div::quoteJSvalue API function in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x…

MediumCVSS 4.3 · v2.0—No exploit Fix available

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: 0.95% (FIRST EPSS); higher than 61.8% of all records.
  • Fixed version: typo3-src (Debian:4.0) 4.0.2+debian-9; typo3-src (Debian:5.0) 4.2.5-1+lenny2; typo3/cms-core (Packagist) 4.1.13, 4.2.10, 4.3beta2.

Low priority for now. Upgrade to typo3-src (Debian:4.0) 4.0.2+debian-9; typo3-src (Debian:5.0) 4.2.5-1+lenny2; typo3/cms-core (Packagist) 4.1.13, 4.2.10, 4.3beta2 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

Cross-site scripting (XSS) vulnerability in the t3lib_div::quoteJSvalue API function in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors related to the sanitizing algorithm.

Published
Nov 2, 2009
Updated
Jun 16, 2026
EPSS
0.9% · 61th 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 · 0.9%

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-3633

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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
typo3typo3

Affected versions

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

  • typo3 typo3up to 4.0.12 inclusive
  • typo3 typo30.1.2
  • typo3 typo31.0.14
  • typo3 typo31.1
  • typo3 typo31.1.09
  • typo3 typo31.1.1
  • typo3 typo31.1.10
  • typo3 typo31.2.0

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:4.0typo3-srcbefore 4.0.2+debian-94.0.2+debian-9
Debian:5.0typo3-srcbefore 4.2.5-1+lenny24.2.5-1+lenny2
Packagisttypo3/cms-corefrom 4.1.0 · before 4.1.134.1.13
Packagisttypo3/cms-corefrom 4.2.0 · before 4.2.104.2.10
Packagisttypo3/cms-corefrom 4.3alpha1 · before 4.3beta24.3beta2
Packagisttypo3/cms-coreup to and including 4.0.13—

Other highest-scoring records for the same primary product.

  • CVE-2009-0255The System extension Install tool in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 creates the encryption key…
    60This week
  • CVE-2013-6288Unspecified vulnerability in the Apache Solr for TYPO3 (solr) extension before 2.8.3 for TYPO3 has unknown impact and remote attack…
    41Plan
  • CVE-2013-5303Unspecified vulnerability in the Store Locator (locator) extension before 3.1.5 for TYPO3 has unknown impact and remote attack vectors…
    41Plan

Published before and after this one in the same product

  • ← EarlierCVE-2009-3631Nov 2, 2009 · The Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2, when the DAM…
    35Monitor
  • ← EarlierCVE-2009-3632Nov 2, 2009 · SQL injection vulnerability in the traditional frontend editing feature in the Frontend Editing subcomponent in TYPO3 4.0.13 and earlier, 4.
    26Monitor
  • Later →CVE-2009-3634Nov 2, 2009 · Cross-site scripting (XSS) vulnerability in the Frontend Login Box (aka felogin) subcomponent in TYPO3 4.2.0 through 4.2.6 allows remote…
    18Monitor

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:typo3-src4.0.2+debian-9 · Debian:4.0Package registry (OSV)
Packagist:typo3/cms-core4.1.13Package registry (OSV)
Packagist:typo3/cms-core4.2.10Package registry (OSV)
Packagist:typo3/cms-core4.3beta2Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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

    State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.

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

    Vulnerable

    ts
    app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);

    Fixed

    ts
    app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    References

    All records