dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1324

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 QQWorld Auto Save Images plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the save_remote_images_get_auto_saved_results() function hooked via a norpriv AJAX in all versions up to, and including, 1.9.8. This makes it possible for unauthenticated attackers to retrieve the contents of arbitrary posts that may not be public.

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 QQWorld Auto Save Images WordPress plugin has a missing capability check on the save_remote_images_get_auto_saved_results() AJAX function, making it accessible to unauthenticated users (hooked via 'nopriv'). This allows attackers to retrieve the contents of arbitrary posts including private, draft, or password-protected posts by manipulating post IDs.

MitigationUpdate the plugin to version 1.9.9 or later which adds proper capability verification. If no update is available, disable the plugin and add a WAF rule to block the vulnerable AJAX endpoint until a patch is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify plugin is installed
    Check the WordPress plugins directory for 'QQWorld Auto Save Images' or look in wp-content/plugins for a folder named 'qqworld-auto-save-images'
    Affected if The plugin folder exists on the server
  2. Check installed version
    Read the main plugin file (usually qqworld-auto-save-images.php) and look for the 'Version' header in the plugin comment block, or query the WordPress database wp_options table for the 'qqworld_auto_save_images_version' option
    Affected if Version is lower than 1.9.9 or the version cannot be determined (older installation)
  3. Identify vulnerable AJAX endpoint
    Search plugin PHP files for 'save_remote_images_get_auto_saved_results' and check if it is hooked to a WordPress AJAX action, typically with add_action('wp_ajax_save_remote_images_get_auto_saved_results', ...) or add_action('wp_ajax_nopriv_save_remote_images_get_auto_saved_results', ...)
    Affected if The function is hooked to wp_ajax_nopriv_ (unauthenticated access) or lacks a capability check (current_user_can) inside the function
  4. Test unauthenticated access
    Send a GET or POST request to /wp-admin/admin-ajax.php with action=save_remote_images_get_auto_saved_results and a post_id parameter (e.g., post_id=1) without authentication cookies
    Affected if The server returns a valid response containing post content rather than a 403 or 401 error or requires login

The environment is affected if the QQWorld Auto Save Images plugin is installed with a version before 1.9.9 and the vulnerable AJAX endpoint is accessible to unauthenticated users (wp_ajax_nopriv hook exists).

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 the plugin to version 1.9.9 or later which adds proper capability verification. If no update is available, disable the plugin and add a WAF rule to block the vulnerable AJAX endpoint until a patch is released.

Recommended fix High confidence

1.9.9

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find QQWorld Auto Save Images in the plugin list
  4. Check if an update is available and click 'Update Now'
  5. Alternatively, manually download version 1.9.9 from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 1.9.8 or higher

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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