Disabled Source, Disabled Right Click and Content Protection · Security record
Is Disabled Source, Disabled Right Click and Content Protection safe?
No known vulnerabilities are on record for Disabled Source, Disabled Right Click and Content Protection.
Checked 4 days ago against the WPVulnerability database, for version 1.8.4.
How it’s looked after
- Last release
- Oct 24, 2026 (2 weeks ago)
- Releases in the last year
- 18
- Tested up to
- WordPress 7.1.4
- Support resolved
- 2 of 2 threads in two months
- Active installs
- 10K+
Known vulnerabilities
None on record for Disabled Source, Disabled Right Click and Content Protection.
Questions about Disabled Source, Disabled Right Click and Content Protection’s security
Is Disabled Source, Disabled Right Click and Content Protection safe to use?
No known vulnerabilities are on record for Disabled Source, Disabled Right Click and Content Protection. That isn’t a guarantee, so keep it updated like any plugin.
Does Disabled Source, Disabled Right Click and Content Protection have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for Disabled Source, Disabled Right Click and Content Protection.
Is Disabled Source, Disabled Right Click and Content Protection still maintained?
Yes. Its last release was 2 weeks ago. Its authors resolved 2 of the 2 support threads opened in the last two months.
Is Disabled Source, Disabled Right Click and Content Protection compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
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.