Quiz MakerWordPress extension · Ays Pro
CVE-2021-24456
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 · uneditedThe Quiz Maker WordPress plugin before 6.2.0.9 did not properly sanitise and escape the order and orderby parameters before using them in SQL statements, leading to SQL injection issues in the admin dashboard
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 confidenceThe Quiz Maker WordPress plugin before version 6.2.0.9 fails to properly sanitize and escape the order and orderby parameters in admin dashboard SQL queries, allowing authenticated administrators to inject malicious SQL commands through these unsanitized inputs.
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
Quiz MakerWordPress extension
< 6.2.0.9CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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.
-
Verify Quiz Maker plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Quiz Maker' or 'Ays Pro Quiz Maker' in the list of active pluginsAffected if The plugin is not installed or not active - no action needed
-
Check installed Quiz Maker versionIn WordPress admin, go to Plugins > Installed Plugins, find Quiz Maker, and note the version number displayed under the plugin nameAffected if Version is present and is less than 6.2.0.9 - vulnerability may be present
-
Confirm administrator access to WordPressLog into the WordPress admin dashboard and verify you have Administrator role by checking Users > All Users > your username shows 'Administrator' under the Role columnAffected if You have administrator access - the vulnerable code path is reachable
-
Verify plugin files exist for manual inspectionVia file manager or SSH, navigate to /wp-content/plugins/quiz-maker/ and list files. Check if the main plugin file (usually quiz-maker.php) existsAffected if Plugin files exist at this path - installation is confirmed
If Quiz Maker plugin is installed with a version lower than 6.2.0.9 and you have administrator-level access to the WordPress admin dashboard, the environment is affected by this SQL injection vulnerability.
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 data6.2.0.9
Update the Quiz Maker plugin to version 6.2.0.9 or later which implements proper input sanitization and parameterized queries for the order and orderby parameters.
Fix this in Quiz Maker
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24456 — 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-24456 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