# CVE-2011-4273: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via specific parameters in GoAhead Webserver, potentially leading to session hijacking or data theft.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Nov 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wqm3-xvpx-4868

## What is CVE-2011-4273?

CVE-2011-4273 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Nov 2011. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in GoAhead Webserver 2.18 allow remote attackers to inject arbitrary web script or HTML via (1) the group parameter to goform/AddGroup, related to addgroup.asp; (2) the url parameter to goform/AddAccessLimit, related to addlimit.asp; or the (3) user (aka User ID) or (4) group parameter to goform/AddUser, related to adduser.asp.

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

## Which versions are affected by CVE-2011-4273?

It affects 1 product.


Products: Goahead Goahead Webserver.

## How do I fix CVE-2011-4273?

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

## Is CVE-2011-4273 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4273 exists.

Public exploit code:

- GoAhead Web Server 2.18 - 'addgroup.asp?group' Cross-Site Scripting (exploitdb)
- GoAhead Web Server 2.18 - 'addlimit.asp?url' Cross-Site Scripting (exploitdb)
- GoAhead Web Server 2.18 - 'adduser.asp' Multiple Cross-Site Scripting Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-2431](https://insights.sbomify.com/CVE-2002-2431/): Other in n/a (high 7.5)
- [CVE-2009-5111](https://insights.sbomify.com/CVE-2009-5111/): Denial of service in n/a (medium 5.0)
- [CVE-2002-2427](https://insights.sbomify.com/CVE-2002-2427/): Auth bypass in n/a (medium 5.0)
- [CVE-2002-2428](https://insights.sbomify.com/CVE-2002-2428/): Null dereference in n/a (medium 5.0)
- [CVE-2002-2429](https://insights.sbomify.com/CVE-2002-2429/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4273 and fix it if it is affected.

What it is: CVE-2011-4273 is a medium-severity cross-site scripting vulnerability in n/a, published on 3 Nov 2011. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-4273 exists.

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-2011-4273/ (Markdown: https://insights.sbomify.com/CVE-2011-4273/index.md)
```

## Sources

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

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