
Allegiant · Security record
Is Allegiant safe?
One known vulnerability affects the current version (1.2.7), and it has no fix yet.
Checked 5 days ago against the WPVulnerability database, for version 1.2.7.
How it’s looked after
- Last release
- Mar 3, 2021 (5 years ago)
- Releases in the last year
- 0
- Active installs
- 1K+
4 known vulnerabilities
- 1 critical
- 1 medium
- 2 not rated
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20201
- 20231
- 20241
Every known vulnerability in Allegiant
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2024-43329 · Aug 16, 2024 · Wordfence
- critical
Code Injection
Fixed in 1.2.6 · CVE-2020-36708 · Jun 7, 2023 · CVE
Fixed in 1.2.6 · Oct 1, 2020 · Patchstack
Fixed in 1.2.6 · WPScan
Questions about Allegiant’s security
Is Allegiant safe to use?
Yes: 1 known vulnerability affects version 1.2.7, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Allegiant have known security vulnerabilities?
Yes: 1 known vulnerability affects version 1.2.7, according to WPVulnerability’s database.
Is Allegiant still maintained?
Its last release was 5 years ago, so it may no longer be actively maintained.
Hear about the next one first
Track your theme 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 theme updated.