WordPress plugin
Publish 2 Ping.fm security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All Publish 2 Ping.fm vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Cross-Site Request Forgery to Stored Cross-Site Scripting via 'wpPingPingKey' Parameter ≤1.1No patch available | CVE-2026-6702 |
- Medium6.1Cross-Site Request Forgery to Stored Cross-Site Scripting via 'wpPingPingKey' Parameter
≤1.1No patch available
Publish 2 Ping.fm: common questions
Does Publish 2 Ping.fm have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Publish 2 Ping.fm: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Publish 2 Ping.fm I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Publish 2 Ping.fm vulnerability?
CVE-2026-6702, published May 4, 2026: Publish 2 Ping.fm <= 1.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting via 'wpPingPingKey' Parameter. Severity: Medium (CVSS 6.1).
Is any Publish 2 Ping.fm vulnerability listed in CISA KEV?
No. None of the known Publish 2 Ping.fm vulnerabilities is currently listed in the CISA KEV catalog.