Is Account Engagement safe?

No known vulnerability affects the current version (2.1.2). 1 issue was found in earlier versions and fixed, the latest disclosed on Apr 12, 2024.

Checked 2 days ago against the WPVulnerability database, for version 2.1.2.

How it’s looked after

Last release: Jun 3, 2024 (2 years ago)
Releases in the last year: 0
Tested up to: WordPress 6.4.14 (current: 7.1)
Active installs: 2K+

1 known vulnerability

1 medium

None affects the current version.

Every known vulnerability in Account Engagement

Newest first, with any that affect the current version at the top.

medium
Missing Authorization
Fixed in 2.1.1 · CVE-2024-32148 · Apr 12, 2024 · Wordfence

Questions about Account Engagement’s security

Is Account Engagement safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Account Engagement updated: most attacks target sites that haven’t updated.

Does Account Engagement have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Account Engagement up to date.

Is Account Engagement still maintained?

Its last release was 2 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.

Is Account Engagement compatible with the latest WordPress?

Account Engagement’s readme says it’s tested up to WordPress 6.4.14, 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 free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.