User Specific Content · Security record
Is User Specific Content safe?
One known vulnerability affects the current version (1.0.6), and it has no fix yet.
Checked 2 days ago against the WPVulnerability database, for version 1.0.6.
How it’s looked after
- Last release
- Nov 28, 2017 (8 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 4.7.0 (current: 7.1)
- Active installs
- 1K+
1 known vulnerability
- 1 not rated
1 affects the current version. 1 has no fix yet.
Every known vulnerability in User Specific Content
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2025-62749 · Dec 31, 2025 · Wordfence
Questions about User Specific Content’s security
Is User Specific Content safe to use?
Yes: 1 known vulnerability affects version 1.0.6, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does User Specific Content have known security vulnerabilities?
Yes: 1 known vulnerability affects version 1.0.6, according to WPVulnerability’s database.
Is User Specific Content still maintained?
Its last release was 8 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is User Specific Content compatible with the latest WordPress?
User Specific Content’s readme says it’s tested up to WordPress 4.7.0, 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.