dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-11323

HIGH · 8.8 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
The AI Quiz | Quiz Maker plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the ai_quiz_update_style() function in all versions up to, and including, 1.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 confidence

The AI Quiz | Quiz Maker WordPress plugin has a missing capability check on the ai_quiz_update_style() function, allowing any authenticated user with Subscriber-level access or higher to update arbitrary WordPress options. This flaw enables attackers to modify the default registration role to Administrator and enable user registration, facilitating complete site compromise through privilege escalation.

MitigationUpdate to version 1.2 or later which implements proper capability checks. Alternatively, remove the plugin if not needed. Audit existing user accounts for unauthorized administrative accounts created via this vulnerability.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'AI Quiz | Quiz Maker' or check the wp-content/plugins/ai-quiz-maker directory exists
    Affected if Plugin is installed and active
  2. Check plugin version
    In Plugins list, find the version number under the plugin name, or inspect ai-quiz-maker/index.php and look for 'Version:' in the plugin header comment
    Affected if Version is unknown, unlisted, or below 1.2
  3. Verify user registration is enabled
    Go to WordPress Settings > General > Membership: ensure 'Anyone can register' is unchecked. Alternatively, check the 'users_can_register' option in wp_options table
    Affected if User registration is enabled on the site
  4. Check default new user role
    Go to Settings > General > Default Role dropdown, or query wp_options for 'default_role' option value
    Affected if Default role is set to Administrator or any elevated role
  5. Audit for unauthorized admin accounts
    Go to Users > All Users and review all accounts with Administrator role. Check user_registered date and compare against expected account creation. Query wp_users and wp_usermeta for Administrator role users you do not recognize
    Affected if There are Administrator accounts you did not create or that were created during an attack period

A site is affected if the AI Quiz plugin is installed and the WordPress user registration setting is enabled or unauthorized Administrator accounts exist.

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

Update to version 1.2 or later which implements proper capability checks. Alternatively, remove the plugin if not needed. Audit existing user accounts for unauthorized administrative accounts created via this vulnerability.

Recommended fix Moderate confidence

Update to the latest version of AI Quiz | Quiz Maker plugin (version higher than 1.1)

  1. Check the current version of the AI Quiz | Quiz Maker plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the AI Quiz | Quiz Maker plugin and note the current version
  4. If the installed version is 1.1 or lower, update the plugin to the latest available version from the WordPress plugin repository
  5. After updating, verify the ai_quiz_update_style() function now includes proper capability checks (e.g., current_user_can('manage_options'))
  6. Consider reviewing user roles and capabilities on the site to ensure no unauthorized administrative accounts were created during the attack

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11323 — 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-2024-11323 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