Skip to content
PluginCanary

TOCHAT.BE

by César Martín · 700+ active installs · Checked 3 Nov 2026
Avoid1 Critical2 Warnings

Avoid: vulnerability published 22 Sep 2025 still has no fix after 14 days.

39/ 100 Canary Score

Capped at 39: a vulnerability has no patch.

Sub-scores for TOCHAT.BE
Ownership100
Maintenance20
Security35
Support70
Reputation70

How the score works

Quick answers

Is TOCHAT.BE still maintained?
No. Last release 18 Feb 2025, over 1 year ago. 18 Feb 2025 · wordpress.org
Who owns TOCHAT.BE, and has it changed hands?
No change recorded. Main committer cesarmartin2019 since Jan 2020. 3 Nov 2026 · SVN log
Was TOCHAT.BE removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is TOCHAT.BE safe?
No. 1 known vulnerability has no fix in the current version. 22 Sep 2025 · Wordfence Intelligence
Is the latest TOCHAT.BE update safe to install?
No ownership change before 1.3.4. No one-star spike after it. 18 Feb 2025 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalSEC-2Vulnerability published 22 Sep 2025 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.6 Oct 2025Evidence
  • WarningMNT-2Tested up to WordPress 6.7.11, 4 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
  • WarningMNT-1No release in 20 months (last release 18 Feb 2025). Plan a replacement if the plugin is important to your site.18 Feb 2026Evidence

Ownership timeline

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

Committers and their active periods
plugin-master21 Jan 2020 to 21 Jan 2020, 1 commits
cesarmartin201922 Jan 2020 to 18 Feb 2025, 33 commits

2 committers recorded. No ownership change since 2020.

Maintenance

Last release
21 months ago
Releases, 24 months
1
Tested up to
6.7 vs 7.1
Requires PHP
5.6 supported 8.2+
Releases per quarter
Releases per quarter for TOCHAT.BE
Q1 20240
Q2 20240
Q3 20243
Q4 20240
Q1 20251
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20260
Q4 20260

Last release 18 Feb 2025. Tested up to 6.7, 4 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

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

Security record

1 vulnerability in 24 months (2 on record), 1 with no fix in the current version.

PublishedIssueCVSSAffectedFixed inDays to patch
22 Sep 2025TOCHAT.BE <= 1.3.4 - Cross-Site Request Forgery4.3<= 1.3.4No fixn/a
Show 1 patched vulnerability
PublishedIssueCVSSAffectedFixed inDays to patch
9 Jul 2024TOCHAT.BE <= 1.3.1 - Unauthenticated Stored Cross-Site Scripting7.2<= 1.3.11.3.2n/a

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

Support

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

Momentum

700+ active installs. History builds with each weekly snapshot.

Momentum history builds with each snapshot.

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

Version1.3.4
AuthorCésar Martín
Added22 Jan 2020
Last updated18 Feb 2025
Active installs700+
Requires WordPress5.0
Tested up to6.7.11
Requires PHP5.6
CategoryCommunication & Messaging > SMS & Text Messaging
Tagschat, whatsapp, click to chat, whatsapp business, whatsapp support chat

Questions

Is TOCHAT.BE still maintained?

No. Last release 18 Feb 2025, over 1 year ago.

Who owns TOCHAT.BE, and has it changed hands?

No change recorded. Main committer cesarmartin2019 since Jan 2020.

Was TOCHAT.BE removed from wordpress.org?

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

Is TOCHAT.BE safe?

No. 1 known vulnerability has no fix in the current version.

Is the latest TOCHAT.BE update safe to install?

No ownership change before 1.3.4. 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