dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10574

HIGH · 7.2 CVSS v3.1 Published 2025-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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 Quiz Maker Business, Developer, and Agency plugins for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'ays_save_google_credentials' function in all versions up to, and including, 8.8.0 (Business), up to, and including, 21.8.0 (Developer), and up to, and including, 31.8.0 (Agency). This makes it possible for unauthenticated attackers to modify the Google Sheets integration credentials within the plugin's settings. Because the 'client_id' parameter is not sanitized or escaped when used in output, this vulnerability could also be leveraged to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

This WordPress plugin vulnerability allows unauthenticated attackers to modify Google Sheets integration credentials due to a missing capability check on the 'ays_save_google_credentials' function. Additionally, the client_id parameter is not sanitized before output, enabling stored XSS attacks when users access affected pages.

MitigationUpdate the plugin to the latest patched version and ensure all Google credentials settings are reviewed for unauthorized changes. Implement proper capability checks and input sanitization on the affected function.

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

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

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

  1. Identify the AYS plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for a plugin with 'AYS' or 'Quiz Maker' in the name. Note the installed version displayed.
    Affected if The plugin is installed and the version is unpatched (prior to the fix release date)
  2. Locate the vulnerable function
    Access the WordPress site via FTP or file manager and navigate to /wp-content/plugins/[ays-plugin-folder]/includes/ or similar directory. Search for the file containing 'ays_save_google_credentials' function.
    Affected if The function 'ays_save_google_credentials' exists in the plugin code without a capability check (current_user_can or similar permission verification)
  3. Verify Google Sheets integration is configured
    In WordPress admin, look for Google Sheets or Google Drive settings within the AYS plugin settings panel. Check if any Google client_id or client_secret fields are present.
    Affected if Google Sheets integration is enabled or configured in the plugin settings
  4. Inspect the client_id parameter handling
    Examine the source code where the client_id parameter is processed and output. Look for missing sanitization functions like esc_attr() or esc_html() before echo/print statements.
    Affected if The client_id value is output directly without sanitization, allowing stored XSS
  5. Check for unauthorized credential modifications
    Review the current Google credentials stored in the database (wp_options table with option_name containing 'google' or 'ays_google') or inspect the plugin settings page for unexpected client_id values.
    Affected if The stored client_id contains unexpected values, scripts, or malicious content

A defender is affected if the AYS/Quiz Maker plugin is installed with an unpatched version and has Google Sheets integration enabled, with the vulnerable function accessible without authentication and client_id output lacking sanitization.

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

Update the plugin to the latest patched version and ensure all Google credentials settings are reviewed for unauthorized changes. Implement proper capability checks and input sanitization on the affected function.

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-10574 — 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-10574 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