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

> Authenticated administrators can inject JavaScript into the login block message, leading to privilege escalation and potential code execution.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hv4w-g3mp-j6rw

## What is CVE-2007-3818?

CVE-2007-3818 is a low-severity cross-site scripting vulnerability in n/a, published on 17 Jul 2007. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the LoginToboggan module 5.x-1.x-dev before 20070712 for Drupal allows remote authenticated users with "administer blocks" permission to inject arbitrary JavaScript and gain privileges via "the message displayed above the default user login block."

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

It affects 1 product.


Products: Drupal Logintoboggan Module.

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

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

## Is CVE-2007-3818 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3817](https://insights.sbomify.com/CVE-2007-3817/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3818 is a low-severity cross-site scripting vulnerability in n/a, published on 17 Jul 2007. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-3818 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-3818/ (Markdown: https://insights.sbomify.com/CVE-2007-3818/index.md)
```

## Sources

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

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