dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15360

CRITICAL · 9.1 CVSS v3.1 Published 2026-08-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 14 days old

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 Ajax Load More WordPress plugin before 8.0.1 does not properly sanitise and escape a parameter before using it in a SQL query, allowing unauthenticated attackers to perform time-based blind SQL injection and extract sensitive data from the database.

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 Ajax Load More WordPress plugin before version 8.0.1 contains an unauthenticated SQL injection vulnerability due to improper sanitization and escaping of a parameter before its use in a SQL query. Attackers can exploit this time-based blind SQL injection to extract sensitive data from the database.

MitigationUpdate Ajax Load More to version 8.0.1 or later immediately. If immediate update is not possible, consider restricting access to the affected endpoints or temporarily disabling the plugin.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Ajax Load More plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ajax Load More' in the list. Note whether it is activated.
    Affected if The plugin is installed and active in WordPress
  2. Check installed version number
    In the Plugins list, click on 'Ajax Load More' to view plugin details, or check the plugin header in /wp-content/plugins/ajax-load-more/ajax-load-more.php for the 'Version' field. Compare this version to 8.0.1.
    Affected if The installed version is lower than 8.0.1 (e.g., 8.0.0, 7.x, 6.x, etc.)
  3. Identify the vulnerable endpoint
    Review the plugin's shortcode and AJAX handlers. The vulnerability exists in the parameter handling for the Ajax query processing. Look for PHP files handling admin-ajax.php or front-end ajax requests within the plugin directory.
    Affected if The plugin handles a parameter that is used in a SQL query without proper sanitization (the exact parameter name is not specified in the CVE summary)
  4. Test for unauthenticated access
    Attempt to access the plugin's AJAX endpoints (typically /wp-admin/admin-ajax.php with action=alm_*) without authentication. The vulnerability is exploitable by unauthenticated attackers.
    Affected if The AJAX endpoint is accessible without authentication and processes user-supplied parameters into SQL queries

Your environment is affected if the Ajax Load More plugin is installed with a version lower than 8.0.1 and the vulnerable AJAX endpoint is accessible without authentication.

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 Ajax Load More to version 8.0.1 or later immediately. If immediate update is not possible, consider restricting access to the affected endpoints or temporarily disabling the plugin.

Recommended fix High confidence

Ajax Load More version 8.0.1

  1. 1. Back up your WordPress site database and files.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the 'Ajax Load More' plugin in the plugin list.
  4. 4. If an update is available, click 'Update Now' to upgrade to version 8.0.1.
  5. 5. Alternatively, download Ajax Load More version 8.0.1 from the official WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version shows 8.0.1 in the plugins list.
  7. 7. Test that Ajax Load More functionality works correctly on your site.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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