Current Menu Item for Custom Post Types · Security record
Is Current Menu Item for Custom Post Types safe?
No known vulnerability affects the current version (1.6). 1 issue was found in earlier versions and fixed, the latest disclosed on Oct 26, 2023.
Checked 3 days ago against the WPVulnerability database, for version 1.6.
How it’s looked after
- Last release
- Nov 26, 2024 (1 year ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.7.11 (current: 7.1)
- Active installs
- 2K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in Current Menu Item for Custom Post Types
Newest first, with any that affect the current version at the top.
Fixed in 1.6 · CVE-2023-46781 · Oct 26, 2023 · Wordfence
Questions about Current Menu Item for Custom Post Types’s security
Is Current Menu Item for Custom Post Types safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Current Menu Item for Custom Post Types updated: most attacks target sites that haven’t updated.
Does Current Menu Item for Custom Post Types have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Current Menu Item for Custom Post Types up to date.
Is Current Menu Item for Custom Post Types still maintained?
Its last release was 1 year ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is Current Menu Item for Custom Post Types compatible with the latest WordPress?
Current Menu Item for Custom Post Types’s readme says it’s tested up to WordPress 6.7.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 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.