dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-6495

HIGH · 7.1 CVSS v3.1 Published 2026-05-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 7.8.4 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin

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 7.8.4 contains a reflected Cross-Site Scripting (XSS) vulnerability. The plugin fails to properly sanitize and escape a user-controlled parameter before outputting it back into the HTML page, allowing an attacker to inject malicious JavaScript code that executes in the context of a victim's browser session.

MitigationUpdate the Ajax Load More plugin to version 7.8.4 or later to obtain the patched code that properly sanitizes and escapes output parameters.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Confirm Ajax Load More plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ajax Load More' in the list, or check the plugin files in /wp-content/plugins/ajax-load-more/ for the main PHP file
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin Plugins list, click on 'Ajax Load More' to view details and note the version number displayed, or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if Version is lower than 7.8.4 (e.g., 7.8.3, 7.8.2, etc.)
  3. Verify the plugin is active
    In WordPress admin > Plugins, confirm the Ajax Load More plugin shows as 'Active'
    Affected if Plugin is active and version is below 7.8.4
  4. Identify vulnerable parameter usage
    Review page sources or use browser developer tools to find where Ajax Load More outputs user-supplied parameters (such as in shortcode attributes or query parameters) without proper escaping
    Affected if User-controlled input is reflected in HTML output without sanitization

You are affected if the Ajax Load More plugin is installed, active, and running a version earlier than 7.8.4, with the vulnerable parameter accessible on your site.

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 Ajax Load More plugin to version 7.8.4 or later to obtain the patched code that properly sanitizes and escapes output parameters.

Recommended fix High confidence

7.8.4

  1. 1. Create a full backup of your WordPress site (database and files) before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate 'Ajax Load More' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install version 7.8.4 or later
  5. 5. Alternatively, download version 7.8.4 from the WordPress plugin repository and upload/install manually
  6. 6. After updating, verify the plugin is running version 7.8.4 or higher in the Plugins list
  7. 7. Clear any site caches if you use caching plugins
  8. 8. 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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