CVE-2021-36863
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in ExpressTech Quiz And Survey Master plugin <= 7.3.4 on WordPress.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in the Quiz And Survey Master WordPress plugin versions 7.3.4 and below. Authenticated users with contributor-level access or higher can inject malicious JavaScript code into quiz or survey fields that are stored in the database and executed when other users (including administrators) view the affected content.
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.3.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.
-
Verify Quiz And Survey Master plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Quiz And Survey Master' or 'Expresstech Quiz And Survey Master'. Note the installed version displayed next to the plugin name.Affected if The plugin is listed in the active WordPress installation.
-
Determine installed plugin versionRead the version number shown in the plugins list. Compare it to the affected range: versions 7.3.4 and below are vulnerable.Affected if The installed version is 7.3.4 or lower.
-
Identify contributor-level or higher usersIn WordPress admin, go to Users > All Users and review the Role column. Look for users assigned 'Contributor', 'Author', 'Editor', or Administrator roles, as these can exploit the flaw.Affected if Any user account with Contributor role or higher exists on the site.
-
Inspect quiz and survey entries for suspicious contentAccess the plugin's quiz/survey results via the WordPress admin panel (typically under QSM or Quiz And Survey Master menu). Examine stored entries in quiz fields for script tags, javascript: URIs, or HTML event attributes that may indicate injected XSS payloads.Affected if Any quiz or survey entries contain unsanitized script tags, event handlers, or JavaScript code in input fields.
-
Review database for stored XSS patternsIf database access is available, query the plugin's tables (commonly named like wp_qsm_*) for patterns such as '<script', 'javascript:', 'onerror=', 'onload=' within quiz field data.Affected if Database records contain script tags or event handler attributes in quiz/survey fields.
If the Quiz And Survey Master plugin is installed at version 7.3.4 or below AND contributor-level users exist on the site AND malicious scripts are found stored in quiz data, the environment is vulnerable to CVE-2021-36863.
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.
dbcve · scopedUpdate the Quiz And Survey Master plugin to version 7.3.5 or later. If immediate patching is not possible, disable the plugin until an update can be applied, as contributor-level users can exploit this vulnerability.
Latest version available on wordpress.org (7.3.5 or higher, as 7.3.4 was the vulnerable release)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Quiz And Survey Master' (ExpressTech) in the plugin list
- Click 'Update Now' if an update is available, or click 'Delete' and reinstall the latest version from wordpress.org
- Verify the update completed successfully
- Test quiz creation and survey functionality to ensure the plugin works correctly after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36863 — 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-2021-36863 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