CVE-2009-4877
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities in WebGUI before 7.7.14 allow remote attackers to hijack the authentication of users for unspecified requests via unknown vectors.
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 · moderate confidenceWebGUI versions prior to 7.7.14 contain multiple cross-site request forgery (CSRF) vulnerabilities that allow remote attackers to trick authenticated users into unknowingly executing unintended actions. The specific attack vectors and affected requests are not detailed in the available documentation, but CSRF attacks typically exploit session cookies without the user's awareness.
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<= 7.7.13= 7.3.12= 7.3.13= 7.3.14= 7.3.15= 7.3.16= 7.3.17= 7.3.18= 7.3.19= 7.3.20= 7.3.21= 7.3.22CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Identify installed WebGUI versionLog into the WebGUI administrative interface and navigate to the 'System' or 'About' section to view the version number. Alternatively, check the version file in the WebGUI installation directory if you have filesystem access.Affected if The displayed version is 7.7.13 or lower, or one of these: 7.3.12, 7.3.13, 7.3.14, 7.3.15, 7.3.16, 7.3.17, 7.3.18, 7.3.19, 7.3.20, 7.3.21, or 7.3.22
-
Verify WebGUI is accessible over the networkConfirm that the WebGUI application is accessible from network locations. Check your web server configuration or firewall rules to determine if the application port (typically 80 or 443) is exposed to untrusted networks or the internet.Affected if WebGUI is reachable from untrusted network segments or the internet, creating the possibility for cross-site attacks.
-
Confirm active user sessions existReview authentication logs or session management settings to determine if WebGUI is configured to maintain authenticated user sessions. CSRF exploits require users to have active sessions when they visit malicious sites.Affected if Users can maintain authenticated sessions while browsing other websites, which is the typical default behavior for WebGUI.
You are affected if your WebGUI version matches any of the listed affected versions (7.7.13 or lower, or any 7.3.12 through 7.3.22) AND the application is accessible to users who could be tricked into visiting malicious sites while authenticated.
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 WebGUI to version 7.7.14 or later to obtain the security patch. As a supplementary defense, implement anti-CSRF tokens in the application and configure proper SameSite cookie attributes.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-4877 — 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-2009-4877 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