Missing AuthorizationWeakness · CWE-862

CVE-2024-49689

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in Harmonic Design HD Quiz – Save Results Light hd-quiz-save-results-light allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects HD Quiz – Save Results Light: from n/a through <= 0.5.

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

Missing authorization vulnerability in the HD Quiz Save Results Light WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to quiz result saving functionality, potentially enabling unauthorized manipulation of quiz data or results.

MitigationImplement proper capability checks and authorization validation in all AJAX handlers and public-facing functions within the plugin. Update to a patched version if available and ensure WordPress nonces are validated for all AJAX requests.

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
None
Integrity
Low
Availability
Low

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

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

  1. Verify HD Quiz Save Results Light plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'HD Quiz Save Results Light' in the list
    Affected if plugin is installed and active
  2. Determine installed plugin version
    Click on the plugin name in the plugins list or check the plugin header in wp-content/plugins/hd-quiz-save-results-light/filename.php for the Version comment
    Affected if version cannot be confirmed as patched or is earlier than patched release
  3. Identify quiz result saving AJAX endpoints
    Search plugin files for wp_ajax_ and wp_ajax_nopriv_ hooks related to saving results - typically found in main plugin PHP file
    Affected if AJAX handlers exist that process quiz result data
  4. Verify AJAX handlers lack capability checks
    Open the PHP file containing AJAX handlers and search for current_user_can, capability checks, or nonce verification before saving quiz results
    Affected if no current_user_can() or capability validation found before insert/update operations on quiz data
  5. Test unauthenticated access to result saving
    Send a direct POST request to the AJAX endpoint (typically /wp-admin/admin-ajax.php with action=hdq_save_result) without authentication credentials
    Affected if request processes without returning authorization error or 403 status

User is affected if the HD Quiz Save Results Light plugin is active and its AJAX handlers for saving quiz results lack proper capability checks and nonce validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper capability checks and authorization validation in all AJAX handlers and public-facing functions within the plugin. Update to a patched version if available and ensure WordPress nonces are validated for all AJAX requests.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49689 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