CVE-2020-23754
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 · uneditedCross Site Scripting (XSS) vulnerability in infusions/member_poll_panel/poll_admin.php in PHP-Fusion 9.03.50, allows attackers to execute arbitrary code, via the polls feature.
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 confidenceA stored Cross Site Scripting (XSS) vulnerability exists in the poll administration functionality of PHP-Fusion 9.03.50. The vulnerability is located in infusions/member_poll_panel/poll_admin.php, where unsanitized user input in the polls feature allows injection of malicious JavaScript that executes in the browsers of other users viewing the polls, potentially leading to session hijacking or arbitrary code execution.
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= 9.03.50CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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 PHP-Fusion installationCheck for PHP-Fusion by looking for its typical installation directories (e.g., /var/www/html/, /htdocs/) or search for characteristic files like main.php, header.php, or config.php in the web root.Affected if PHP-Fusion is installed on the server.
-
Determine PHP-Fusion versionLocate the version file or check the administration dashboard. The version is typically displayed in the admin panel footer or can be found in version.php or similar files in the includes or root directory.Affected if The installed version is exactly 9.03.50.
-
Verify poll feature is enabledCheck if the member_poll_panel infusion is enabled. This can be done by examining the infusions table in the database or by accessing the Admin Panel > System > Infusions and looking for 'Member Poll Panel' in the list of active infusions.Affected if The Member Poll Panel infusion is enabled and active.
-
Check for poll administration accessVerify if the poll_admin.php file exists at infusions/member_poll_panel/poll_admin.php within the PHP-Fusion installation directory. Also determine if any user accounts have permission to access poll administration (typically checked via user_level or specific poll permissions in the database).Affected if The poll_admin.php file exists and the site has users with poll administration privileges.
A system is affected only if PHP-Fusion version 9.03.50 is installed, the Member Poll Panel infusion is enabled, and users with poll administration access exist to inject the malicious payload.
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 dataImplement strict input validation and context-aware output encoding for all user-supplied data in the poll functionality, and add Content Security Policy headers to mitigate XSS risks.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-23754 — 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-23754 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