CVE-2025-15525

Ajax Load More – Infinite Scroll, Lazy Load & Load More <= 7.8.1 - Incorrect Authorization to Unauthenticated Private/Draft Post Title and Excerpt Exposure

2026-01-30 16:20
shark3y

Strategic Overview

Status
Patched in 7.8.2
Affected Version
<= 7.8.1
CVSS
5.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2025-15525
View all Ajax Load More – Infinite Scroll, Load More, & Lazy Load vulnerabilities

At a glance

CVE-2025-15525 is a medium-severity Incorrect Authorization vulnerability in the Ajax Load More WordPress plugin, affecting versions <= 7.8.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.8.2; sites on affected versions should update now. Disclosed January 2026, reported by shark3y.

Vulnerability Overview

The Ajax Load More – Infinite Scroll, Load More, & Lazy Load plugin for WordPress is vulnerable to unauthorized access of data due to incorrect authorization on the parse_custom_args() function in all versions up to, and including, 7.8.1. This makes it possible for unauthenticated attackers to expose the titles and excerpts of private, draft, pending, scheduled, and trashed posts.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-863: Incorrect Authorization

Ajax Load More <= 7.8.1 carries this weakness at parse_custom_args(), and reaching it takes no account at all. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For Ajax Load More the fix is 7.8.2: builds <= 7.8.1 are affected, anything from 7.8.2 onward is not.

Remediation

Update to version 7.8.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Ajax Load More 7.8.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C