# CVE-2011-2157: Information disclosure in n/a

> Remote attackers can obtain sensitive email addresses by reading default form field values in SmarterStats admin pages.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g5gc-p4g2-fgw7

## What is CVE-2011-2157?

CVE-2011-2157 is a medium-severity vulnerability in n/a, published on 20 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The (1) Admin/frmEmailReportSettings.aspx and (2) Admin/frmGeneralSettings.aspx components in the SmarterTools SmarterStats 6.0 web server generate web pages containing e-mail addresses, which allows remote attackers to obtain potentially sensitive information by reading the default values of form fields.

Weakness: CWE-264

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

It affects 1 product.


Products: Smartertools Smarterstats.

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

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

## Is CVE-2011-2157 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4752](https://insights.sbomify.com/CVE-2011-4752/): Other in n/a (critical 10.0)
- [CVE-2011-2148](https://insights.sbomify.com/CVE-2011-2148/): Command injection in n/a (critical 10.0)
- [CVE-2011-2158](https://insights.sbomify.com/CVE-2011-2158/): Other in n/a (critical 10.0)
- [CVE-2011-2159](https://insights.sbomify.com/CVE-2011-2159/): Other in n/a (critical 10.0)
- [CVE-2011-2149](https://insights.sbomify.com/CVE-2011-2149/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2157 is a medium-severity vulnerability in n/a, published on 20 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2157 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-2011-2157/ (Markdown: https://insights.sbomify.com/CVE-2011-2157/index.md)
```

## Sources

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

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