Is Admin Page Spider safe?

No known vulnerability affects the current version (3.37). 1 issue was found in earlier versions and fixed, the latest disclosed on Apr 29, 2024.

Checked 1 day ago against the WPVulnerability database, for version 3.37.

How it’s looked after

Last release: Apr 22, 2026 (6 months ago)
Releases in the last year: 0
Tested up to: WordPress 6.9.11 (current: 7.1)
Active installs: 1K+

1 known vulnerability

1 medium

None affects the current version.

Every known vulnerability in Admin Page Spider

Newest first, with any that affect the current version at the top.

medium
Authenticated (Admin+) Stored Cross-Site Scripting
Fixed in 3.32 · CVE-2024-2401 · Apr 29, 2024 · Wordfence

Questions about Admin Page Spider’s security

Is Admin Page Spider safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Admin Page Spider updated: most attacks target sites that haven’t updated.

Does Admin Page Spider have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Admin Page Spider up to date.

Is Admin Page Spider still maintained?

Its last release was 6 months ago. No support threads were opened in the last two months.

Is Admin Page Spider compatible with the latest WordPress?

Admin Page Spider’s readme says it’s tested up to WordPress 6.9.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.