dbcve.org
Wdja CmsApplication · Wdja

CVE-2020-20982

CRITICAL · 9.6 CVSS v3.1 Published 2021-11-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross Site Scripting (XSS) vulnerability in shadoweb wdja v1.5.1, allows attackers to execute arbitrary code and gain escalated privileges, via the backurl parameter to /php/passport/index.php.

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 confidence

Cross-Site Scripting (XSS) vulnerability in shadoweb wdja v1.5.1 allows remote attackers to inject malicious scripts through the unsanitized 'backurl' parameter in /php/passport/index.php, potentially leading to arbitrary code execution and privilege escalation.

MitigationImplement strict input validation and output encoding for the backurl parameter; sanitize all user-supplied input before reflecting it in HTML/JavaScript responses.

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
Wdja CmsApplication
Affected:= 1.5.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Wdja CMS installation and version
    Locate the Wdja CMS installation directory and check for version indicators such as version files, readme files, or admin dashboard about pages. Compare the installed version to the affected range (1.5.1).
    Affected if The installed version is exactly 1.5.1 or falls within unpatched versions of this release.
  2. Verify vulnerable file exists
    Check if the file /php/passport/index.php exists within the web application directory.
    Affected if The vulnerable file exists in the installation.
  3. Inspect backurl parameter handling
    Review the source code of /php/passport/index.php to determine if the 'backurl' parameter is processed and reflected in the response without proper sanitization or output encoding.
    Affected if The backurl parameter is accepted and echoed back without sanitization or encoding.
  4. Test for XSS via backurl parameter
    If testing is authorized, submit a crafted request to /php/passport/index.php with a malicious script in the backurl parameter (e.g., backurl=javascript:alert(1)) and observe if the script executes in the response.
    Affected if The unsanitized backurl parameter is reflected in HTML/JavaScript context without encoding.

The environment is affected if Wdja CMS version 1.5.1 is installed and the /php/passport/index.php file processes the backurl parameter without input validation or output encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and output encoding for the backurl parameter; sanitize all user-supplied input before reflecting it in HTML/JavaScript responses.

Recommended fix Moderate confidence

Check wdja CMS GitHub for version > 1.5.1 that addresses the XSS in backurl parameter

  1. 1. Navigate to the official Wdja CMS GitHub repository or download page
  2. 2. Check for releases or commits after version 1.5.1 that address CVE-2020-20982
  3. 3. If a fixed version is available, download the complete upgrade package
  4. 4. Back up the existing database and all website files before upgrading
  5. 5. Replace the existing installation files with the new version files
  6. 6. Test the /php/passport/index.php endpoint with the backurl parameter to verify the XSS vulnerability is fixed
  7. 7. Verify that the application functions normally after the upgrade
Caveat Review release notes for any breaking changes between 1.5.1 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wdja Cms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-20982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-20982 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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