My YouTube Channel · Security record
Is My YouTube Channel safe?
No known vulnerability affects the current version (3.25.2). 5 issues were found in earlier versions and fixed, the latest disclosed on Feb 23, 2023.
Checked 4 days ago against the WPVulnerability database, for version 3.25.2.
How it’s looked after
- Last release
- Feb 8, 2025 (1 year ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.7.11 (current: 7.1)
- Active installs
- 5K+
5 known vulnerabilities
- 4 medium
- 1 not rated
None affects the current version.
Every known vulnerability in My YouTube Channel
Newest first, with any that affect the current version at the top.
Fixed in 3.23.4 · CVE-2023-25987 · Feb 23, 2023 · Wordfence
Fixed in 3.23.0 · CVE-2022-4756 · Jan 11, 2023 · Wordfence
Fixed in 3.23.0 · Jan 6, 2023 · Patchstack
- medium
Missing Authorization
Fixed in 3.23.0 · CVE-2023-0447 · Jan 4, 2023 · Wordfence
Fixed in 3.23.0 · CVE-2023-0446 · Jan 4, 2023 · Wordfence
Questions about My YouTube Channel’s security
Is My YouTube Channel safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep My YouTube Channel updated: most attacks target sites that haven’t updated.
Does My YouTube Channel have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 5 older issues, fixed in earlier versions, so keep My YouTube Channel up to date.
Is My YouTube Channel 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 My YouTube Channel compatible with the latest WordPress?
My YouTube Channel’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.