CVE-2024-9685: The Notification for Telegram plugin for WordPress is vulnerable to unauthorized test message sending due to a

Q: How do I fix CVE-2024-9685?

notification for telegram: upgrade to 3.3.2. Exact commands for each OS are on this page.

Q: Is CVE-2024-9685 being exploited?

CVE-2024-9685 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-9685 affect?

CVE-2024-9685 affects notification for telegram. Severity is medium (CVSS 4.3). The Notification for Telegram plugin for WordPress is vulnerable to unauthorized test message sending due to a missing capability check on the 'nftb_test_action' function in versions up to, and including, 3.3.1. This makes it possible for a

Q: How urgent is CVE-2024-9685?

Priority 21/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2024-9685 is a medium-severity flaw (CVSS 4.3) affecting notification for telegram. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Notification for Telegram plugin for WordPress is vulnerable to unauthorized test message sending due to a missing capability check on the 'nftb_test_action' function in versions up to, and including, 3.3.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to send a test message via the Telegram Bot API to all users configured in the settings.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Weakness	CWE-862
Published	2024-10-10
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: andreamarinucci

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-10-10 02:15 UTCPublished CVE record published
2026-06-17 08:25 UTCUpdated Record last modified

andreamarinucci notification for telegram UPGRADE

Affected: < 3.3.2

Fixed in: 3.3.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy notification-for-telegram || rpm -q notification-for-telegram || notification-for-telegram --version

2. UPGRADE to 3.3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade notification-for-telegram

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade notification-for-telegram

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-9685?

notification for telegram: upgrade to 3.3.2. Exact commands for each OS are on this page.

Is CVE-2024-9685 being exploited?

CVE-2024-9685 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-9685 affect?

CVE-2024-9685 affects notification for telegram. Severity is medium (CVSS 4.3). The Notification for Telegram plugin for WordPress is vulnerable to unauthorized test message sending due to a missing capability check on the 'nftb_test_action' function in versions up to, and including, 3.3.1. This makes it possible for a

How urgent is CVE-2024-9685?

Priority 21/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities · Telegram vulnerabilities

References

← Back to latest CVEs