CVE-2026-48867
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 · uneditedUnauthenticated Cross Site Scripting (XSS) in Quiz And Survey Master <= 11.1.2 versions.
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 confidenceAn unauthenticated Cross Site Scripting (XSS) vulnerability exists in the Quiz And Survey Master WordPress plugin versions 11.1.2 and below. Attackers can inject malicious scripts through unsanitized user inputs, potentially compromising other users or administrators viewing the affected content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Quiz And Survey Master' in the list. Alternatively, check the /wp-content/plugins/quiz-master-next/ directory exists on the server.Affected if The plugin is installed and active
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Quiz And Survey Master, and note the version number displayed below the plugin name. Alternatively, open /wp-content/plugins/quiz-master-next/readme.txt and check the version in the header.Affected if The version is 11.1.2 or lower
-
Confirm public quiz/survey forms are enabledIn WordPress admin, go to Quiz And Survey Master > Quizzes/Surveys and verify that at least one quiz or survey is published and set to allow public submissions. The XSS payload would be submitted through these public-facing forms.Affected if Publicly accessible quiz or survey forms exist and accept submissions
-
Inspect quiz question and answer fields for suspicious scriptsReview existing quizzes in Quiz And Survey Master > Quizzes/Surveys > Edit. Check all question text, answer options, and result messages for unexpected <script> tags, javascript: URIs, or event handler attributes like onload, onerror, or onclick.Affected if Any quiz contains injected JavaScript code in fields that users can control
A user is affected if Quiz And Survey Master version 11.1.2 or lower is installed, active, and has publicly accessible quiz forms that accept user input.
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 dataUpdate Quiz And Survey Master plugin to a version newer than 11.1.2. If no update is available, consider disabling the plugin until a patch is released.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48867 — 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-2026-48867 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