CVE-2020-7050
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 · uneditedCodologic Codoforum through 4.8.4 allows a DOM-based XSS. While creating a new topic as a normal user, it is possible to add a poll that is automatically loaded in the DOM once the thread/topic is opened. Because session cookies lack the HttpOnly flag, it is possible to steal authentication cookies and take over accounts.
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 confidenceCodoforum through 4.8.4 contains a DOM-based XSS vulnerability in the poll functionality. When a normal user creates a new topic with a poll, malicious script input is not properly sanitized and executes when the thread is loaded in the DOM. Additionally, session cookies lack the HttpOnly flag, allowing stolen authentication cookies to be accessed via JavaScript for account takeover.
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.8.4CVSS 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
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Determine Codoforum versionCheck the version number in the site footer, admin dashboard, or in a version file (commonly in sys/config.php or similar config files in the installation directory)Affected if The installed version is 4.8.4 or any earlier version (e.g., 4.8.3, 4.8.2, etc.)
-
Identify if poll feature is enabledNavigate to the forum as an administrator and check the poll settings in the admin panel (typically under Settings > Poll or similar), or look for poll-related database entries in the polls tableAffected if Poll functionality is enabled and users can create polls in forum topics
-
Inspect page source for poll renderingCreate a test topic with a poll using a non-administrator account, then view the page source or use browser dev tools to inspect the rendered HTML where the poll options appearAffected if The poll data is rendered directly into the HTML/JS without visible sanitization (look for unescaped quote characters or script tags in the DOM)
-
Check session cookie attributesLog into the forum and open browser dev tools (Application/Storage tab), examine the session cookie (commonly named sid, PHPSESSID, or similar) and check the HttpOnly columnAffected if The session cookie does not have the HttpOnly flag set (the HttpOnly column is unchecked or missing)
A user is affected if they are running Codoforum version 4.8.4 or earlier, have the poll feature enabled, and their session cookies lack the HttpOnly flag.
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 dataFix the DOM-based XSS by implementing proper input validation and output encoding on poll data before rendering in the DOM. Configure session cookies to include the HttpOnly flag to prevent JavaScript access.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7050 — 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-2020-7050 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