Skip to content
PluginCanary

Acumbamail

by Acumbamail · 1,000+ active installs · Checked 3 Nov 2026
Healthy

Healthy: maintained, last release 22 Oct 2026, 8 releases in 24 months, no unpatched vulnerabilities.

100/ 100 Canary Score
Sub-scores for Acumbamail
Ownership100
Maintenance100
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Acumbamail still maintained?
Yes. Last release 22 Oct 2026, 8 releases in the last 24 months. 22 Oct 2026 · wordpress.org
Who owns Acumbamail, and has it changed hands?
No change recorded. Main committer jesusbotella since Mar 2014. 3 Nov 2026 · SVN log
Was Acumbamail removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Acumbamail safe?
1 known vulnerability, fixed (latest in 1.0.4.1). Not on the exploited list. 30 Apr 2014 · Wordfence Intelligence
Is the latest Acumbamail update safe to install?
No ownership change before 2.0.31. No one-star spike after it. 22 Oct 2026 · Release history

Active signals

Facts we detected, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
jesusbotella10 Mar 2014 to 22 Oct 2026, 139 commits

1 committer recorded. No ownership change since 2014.

Maintenance

Last release
13 days ago
Releases, 24 months
8
Tested up to
7.1 current
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for Acumbamail
Q1 20240
Q2 20240
Q3 20244
Q4 20243
Q1 20250
Q2 20250
Q3 20250
Q4 20252
Q1 20260
Q2 20261
Q3 20261
Q4 20263

Last release 22 Oct 2026. Tested with WordPress 7.1 (current).

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

Rating distribution
5 star1
4 star0
3 star0
2 star0
1 star0

Security record

1 vulnerability on record, patched (latest fixed in 1.0.4.1).

Show 1 patched vulnerability
PublishedIssueCVSSAffectedFixed inDays to patch
30 Apr 2014Acumbamail < 1.0.4.1 - Sensitive Information Disclosure7.5< 1.0.4.11.0.4.1n/a

Changelog mentions of security fixes: 2.0.31 (security, authorization).

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

Support history appears after our first snapshots of the forum counts.

Momentum

1,000+ active installs. History builds with each weekly snapshot.

Weekly downloads, last 27 weeks
Weekly downloads for Acumbamail
4 May 202618
11 May 202655
18 May 202643
25 May 202652
1 Jun 2026602
8 Jun 2026148
15 Jun 2026104
22 Jun 202687
29 Jun 202688
6 Jul 2026144
13 Jul 202676
20 Jul 202658
27 Jul 202686
3 Aug 202672
10 Aug 202668
17 Aug 202679
24 Aug 202655
31 Aug 202670
7 Sep 2026577
14 Sep 2026267
21 Sep 2026181
28 Sep 2026128
5 Oct 2026100
12 Oct 2026615
19 Oct 20261,263
26 Oct 2026326
2 Nov 202671

Weekly downloads over the last 4 weeks are 183% above the 27-week average.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Version2.0.31
AuthorAcumbamail
Added10 Mar 2014
Last updated22 Oct 2026
Active installs1,000+
Requires WordPress4.7
Tested up to7.1.4
Requires PHP7.4
CategoryMarketing & Advertising > Email Marketing & Campaigns
Tagsmailing, acumbamail, Email Marketing

Questions

Is Acumbamail still maintained?

Yes. Last release 22 Oct 2026, 8 releases in the last 24 months.

Who owns Acumbamail, and has it changed hands?

No change recorded. Main committer jesusbotella since Mar 2014.

Was Acumbamail removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is Acumbamail safe?

1 known vulnerability, fixed (latest in 1.0.4.1). Not on the exploited list.

Is the latest Acumbamail update safe to install?

No ownership change before 2.0.31. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 3 Nov 2026.Report a data issue