CVE-2011-0549
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 · uneditedSQL injection vulnerability in forget.php in the management GUI in Symantec Web Gateway 4.5.x allows remote attackers to execute arbitrary SQL commands via the username parameter.
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 confidenceSQL injection vulnerability in forget.php in the management GUI of Symantec Web Gateway 4.5.x allows remote attackers to execute arbitrary SQL commands via the username parameter. The vulnerability is exploitable without authentication.
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= 4.5= 4.5.0.326= 4.5.1.34= 4.5.1.44= 4.5.2.37= 4.5.2.65= 4.5.2.72= 4.5.3.38= 4.5.4.9CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Confirm product is Symantec Web GatewayIdentify if the target system is running Symantec Web Gateway by checking the product name in the admin interface, about page, or system information.Affected if The product is not Symantec Web Gateway.
-
Check installed version against affected versionsLocate the installed version number in the management GUI (typically in Help > About or System > Status) or via CLI. Compare against the affected versions: 4.5, 4.5.0.326, 4.5.1.34, 4.5.1.44, 4.5.2.37, 4.5.2.65, 4.5.2.72, 4.5.3.38, 4.5.4.9Affected if The installed version exactly matches one of the listed affected versions.
-
Verify forget.php exists in management GUICheck if the file forget.php exists in the web root of the management GUI (typically accessed via HTTPS on port 443). This file handles password recovery functionality.Affected if The forget.php file is present and accessible.
-
Confirm management GUI is network-accessibleVerify that the Symantec Web Gateway management interface is reachable over the network on the expected ports (default HTTPS on 443).Affected if The management GUI is exposed to network access.
You are affected if your installed version of Symantec Web Gateway exactly matches 4.5, 4.5.0.326, 4.5.1.34, 4.5.1.44, 4.5.2.37, 4.5.2.65, 4.5.2.72, 4.5.3.38, or 4.5.4.9 and the management GUI (including forget.php) is accessible.
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 dataApply vendor patches for CVE-2011-0549. If no patch available, restrict network access to the management GUI and consider compensating controls such as WAF rules filtering the username parameter.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0549 — 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-0549 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