CVE-2011-4751
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSmarterTools SmarterStats 6.2.4100 generates web pages containing external links in response to GET requests with query strings for frmGettingStarted.aspx, which makes it easier for remote attackers to obtain sensitive information by reading (1) web-server access logs or (2) web-server Referer logs, related to a "cross-domain Referer leakage" issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSmarterStats 6.2.4100 reflects query string parameters from GET requests to frmGettingStarted.aspx into generated web pages. This causes sensitive data in URLs (session tokens, credentials, or other parameters) to be recorded in web-server access logs and Referer headers, allowing attackers who gain read access to these logs to obtain sensitive information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.2.4100CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SmarterStats versionCheck the installed SmarterStats version via the administration interface under 'About' or by locating the SmarterStats executable and checking its file properties/version infoAffected if The installed version is exactly 6.2.4100
-
Locate frmGettingStarted.aspxVerify that the file frmGettingStarted.aspx exists in the SmarterStats web application directory (typically under the 'Admin' or root web folder)Affected if The file exists and is accessible via HTTP GET requests to the SmarterStats server
-
Test for query string reflectionSend a GET request to frmGettingStarted.aspx with a test query parameter (e.g., ?test=secret123) and examine whether the parameter value appears in the response bodyAffected if The query string parameter is reflected verbatim in the rendered page content
-
Examine web server access logsReview the IIS or SmarterStats access logs for entries involving frmGettingStarted.aspx that contain sensitive query parameters (session IDs, credentials, tokens) in the requested URLAffected if Access logs contain URLs with sensitive query parameters (session tokens, login credentials, API keys) in requests to frmGettingStarted.aspx
-
Review Referer header loggingCheck server logs to see if Referer headers are being logged, particularly entries where Referer URLs contain sensitive query parameters from frmGettingStarted.aspxAffected if Referer logs capture URLs containing sensitive data that originated from frmGettingStarted.aspx
A user is affected if SmarterStats version 6.2.4100 is installed AND the frmGettingStarted.aspx page is accessible, resulting in sensitive query parameters being recorded in access or Referer logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of SmarterStats that addresses the Referer leakage, and ensure strict access controls on web-server access and referer logs to prevent unauthorized reading.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4751 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-4751 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data