WP Maximum Execution Time Exceeded · Security record
Is WP Maximum Execution Time Exceeded safe?
No known vulnerabilities are on record for WP Maximum Execution Time Exceeded.
Checked 5 days ago against the WPVulnerability database, for version 1.0.3.
How it’s looked after
- Last release
- Jan 25, 2021 (5 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 5.6.23 (current: 7.1)
- Active installs
- 20K+
Known vulnerabilities
None on record for WP Maximum Execution Time Exceeded.
Questions about WP Maximum Execution Time Exceeded’s security
Is WP Maximum Execution Time Exceeded safe to use?
No known vulnerabilities are on record for WP Maximum Execution Time Exceeded. That isn’t a guarantee, so keep it updated like any plugin.
Does WP Maximum Execution Time Exceeded have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for WP Maximum Execution Time Exceeded.
Is WP Maximum Execution Time Exceeded still maintained?
Its last release was 5 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is WP Maximum Execution Time Exceeded compatible with the latest WordPress?
WP Maximum Execution Time Exceeded’s readme says it’s tested up to WordPress 5.6.23, 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 freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.