# CVE-2007-1443: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in the registration form of Woltlab Burning Board.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jgp2-gf2q-g62f

## What is CVE-2007-1443?

CVE-2007-1443 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Mar 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in register.php in Woltlab Burning Board (wBB) 2.3.6 and Burning Board Lite 1.0.2pl3e allow remote attackers to inject arbitrary web script or HTML via the (1) r_username, (2) r_email, (3) r_password, (4) r_confirmpassword, (5) r_homepage, (6) r_icq, (7) r_aim, (8) r_yim, (9) r_msn, (10) r_year, (11) r_month, (12) r_day, (13) r_gender, (14) r_signature, (15) r_usertext, (16) r_invisible, (17) r_usecookies, (18) r_admincanemail, (19) r_emailnotify, (20) r_notificationperpm, (21) r_receivepm, (22) r_emailonpm, (23) r_pmpopup, (24) r_showsignatures, (25) r_showavatars, (26) r_showimages, (27) r_daysprune, (28) r_umaxposts, (29) r_dateformat, (30) r_timeformat, (31) r_startweek, (32) r_timezoneoffset, (33) r_usewysiwyg, (34) r_styleid, (35) r_langid, (36) key_string, (37) key_number, (38) disablesmilies, (39) disablebbcode, (40) disableimages, (41) field[1], (42) field[2], and (43) field[3] parameters.  NOTE: a third-party researcher has disputed some of these vectors, stating that only the r_dateformat and r_timeformat parameters in Burning Board 2.3.6 are affected.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2007-1443?

It affects 2 products.


Products: Woltlab Burning Board, Woltlab Burning Board Lite.

## How do I fix CVE-2007-1443?

No fix has been published for CVE-2007-1443 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-1443 being exploited?

There is no known exploitation of CVE-2007-1443 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-0857](https://insights.sbomify.com/CVE-2008-0857/): SQL injection in n/a (high 7.5)
- [CVE-2007-1518](https://insights.sbomify.com/CVE-2007-1518/): SQL injection in n/a (high 7.5)
- [CVE-2007-0388](https://insights.sbomify.com/CVE-2007-0388/): SQL injection in n/a (high 7.5)
- [CVE-2006-5029](https://insights.sbomify.com/CVE-2006-5029/): SQL injection in n/a (high 7.5)
- [CVE-2006-3254](https://insights.sbomify.com/CVE-2006-3254/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1443 and fix it if it is affected.

What it is: CVE-2007-1443 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Mar 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-1443 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-1443/ (Markdown: https://insights.sbomify.com/CVE-2007-1443/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-1443
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-1443
- OSV: https://osv.dev/vulnerability/CVE-2007-1443

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-1443/
Summaries are generated and may contain mistakes; the official description above is the record.