WordPress security by component
Bitly
Plugin description
Bitly is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Sep 22, 2025; the highest CVE/CNA score is 6.5.
Plugin slug:
wp-bitlyLatest vulnerability
CVE-2025-58231: Bitly: Cross-site scripting
Bitly is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
| Safe version |
|
||
|---|---|---|---|
| Sep 22, 2025 |
CVE-2025-58231
Bitly: Cross-site scripting
Bitly is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Jan 09, 2025 |
CVE-2024-12616
Bitly's: A security weakness
Bitly's is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Nov 01, 2024 |
CVE-2024-43209
Bitly: A security weakness
Bitly is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Nov 07, 2023 |
CVE-2023-5577
Bitly's: Cross-site scripting
Bitly's is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.4
NVD5.4
|