HomeWordPress vulnerabilitiesPage-list
Page-list vulnerabilities
Page-list has 2 known vulnerabilities in this database. The most recent published record is dated 6 Jun 2026.
- Known vulnerabilities
- 2
- Active installs
- 30,000+
- Latest version
- 6.3
- Last updated
- 29 May 2026
- Most recent
- 6 Jun 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-9008 | Medium 4.3 | Up to 6.2 | Fixed in a later version (latest 6.3) | 6 Jun 2026 |
| Cross-site scripting (XSS) CVE-2022-4485 | Medium 5.4 | Before 5.3 | Fixed in 5.3 | 23 Jan 2023 |
Read the published descriptions
- CVE-2026-9008, 6 Jun 2026
- The Page-list plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 6.2. This is due to the pagelist_unqprfx_ext_shortcode() function (the [pagelist_ext] / [pagelistext] shortcode) accepting attacker-controlled post_status, post_type, and show_meta_key attributes and passing them directly into get_pages() and get_post_meta() with no capability check verifying that the rendering user is permitted to read the matched objects. When the current post has no child pages, the shortcode re-issues the query with child_of => 0, broadening it to every page on the site matching the supplied status/type. This makes it possible for authenticated attackers, with contributor-level access and above, to disclose the titles, body content/excerpts, and arbitrary post meta of unrelated private and draft pages by inserting the shortcode into a contributor-authored draft and previewing it. CVE record
- CVE-2022-4485, 23 Jan 2023
- The Page-list WordPress plugin before 5.3 does not validate and escape some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks which could be used against high privilege users such as admins. CVE record
What to do if you run Page-list
If you run Page-list, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Page-list vulnerabilities
Free. We email you when a new vulnerability is published for Page-list, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.