WordPress plugin
Peadig’s Google +1 Button 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 Peadig’s Google +1 Button vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting ≤0.1.2No patch available | CVE-2025-46483 |
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤0.1.2No patch available
Peadig’s Google +1 Button: common questions
Does Peadig’s Google +1 Button have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Peadig’s Google +1 Button: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Peadig’s Google +1 Button 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 Peadig’s Google +1 Button vulnerability?
CVE-2025-46483, published Apr 24, 2025: Peadig’s Google +1 Button <= 0.1.2 - Authenticated (Contributor+) Stored Cross-Site Scripting. Severity: Medium (CVSS 6.4).
Is any Peadig’s Google +1 Button vulnerability listed in CISA KEV?
No. None of the known Peadig’s Google +1 Button vulnerabilities is currently listed in the CISA KEV catalog.