Custom Global Variables · Security record
Is Custom Global Variables safe?
No known vulnerability affects the current version (1.1.4). 3 issues were found in earlier versions and fixed, the latest disclosed on Jan 11, 2021.
Checked 5 days ago against the WPVulnerability database, for version 1.1.4.
How it’s looked after
- Last release
- Nov 2, 2026 (6 days ago)
- Releases in the last year
- 2
- Tested up to
- WordPress 7.1.4
- Active installs
- 5K+
3 known vulnerabilities
- 1 medium
- 2 not rated
None affects the current version.
Every known vulnerability in Custom Global Variables
Newest first, with any that affect the current version at the top.
Fixed in 1.1.1 · CVE-2021-3124 · Jan 11, 2021 · Wordfence
Fixed in 1.1.1 · Jan 11, 2021 · Patchstack
Fixed in 1.1.1 · WPScan
Questions about Custom Global Variables’s security
Is Custom Global Variables safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Custom Global Variables updated: most attacks target sites that haven’t updated.
Does Custom Global Variables have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 3 older issues, fixed in earlier versions, so keep Custom Global Variables up to date.
Is Custom Global Variables still maintained?
Yes. Its last release was 6 days ago. No support threads were opened in the last two months.
Is Custom Global Variables 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.