CVE-2022-2945 json
WordPress Infinite Scroll – Ajax Load More <= 5.5.3 - Directory Traversal
published 4y ago modified 4mo ago also EUVD-2022-35166
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
The WordPress Infinite Scroll – Ajax Load More plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 5.5.3 via the 'type' parameter found in the alm_get_layout() function. This makes it possible for authenticated attackers, with administrative permissions, to read the contents of arbitrary files on the server, which can contain sensitive information.
Is CVE-2022-2945 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gist.github.com https://gist.github.com/Xib3rR4dAr/f9a4b4838154854ec6cde7d5deb76bf9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
Affected products
- dcooney Ajax Load More – Infinite Scroll, Load More, & Lazy Load
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
gist.github.com
/Xib3rR4dAr/f9a4b4838154854ec6cde7d5deb76bf9
exploit, third-party-advisory
- wordfence.com /threat-intel/vulnerabilities/id/8957413c-95e0-49c8-ba8a-02b9b5141e08?source=cve
-
plugins.svn.wordpress.org
/ajax-load-more/tags/5.5.4/README.txt
release-notes, third-party-advisory
-
wordfence.com
/vulnerability-advisories/#CVE-2022-2945
third-party-advisory
Sources
- CVE List CVE-2022-2945
- NVD CVE-2022-2945
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.