WordPress security by component
Publitio
Plugin description
Publitio is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Oct 27, 2025; the highest CVE/CNA score is 6.5.
Plugin slug:
publitioLatest vulnerability
CVE-2025-62947: Publitio: A security weakness
Publitio 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.
| Safe version |
|
||
|---|---|---|---|
| Oct 27, 2025 |
CVE-2025-62947
Publitio: A security weakness
Publitio 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 |
CVE5.0
NVDPending
|
| Sep 22, 2025 |
CVE-2025-58962
Publitio: Server-side request forgery
Publitio is affected by server-side request forgery. Exposure depends on how the affected operation is made reachable by the site. The vulnerable server can be induced to make attacker-selected network requests.
|
See mitigation notes |
CVE6.4
NVDPending
|
| Apr 03, 2025 |
CVE-2025-31800
Publitio: Filesystem traversal
Publitio is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.
|
See mitigation notes |
CVE6.5
NVDPending
|
| Apr 01, 2025 |
CVE-2025-31799
Publitio: A security weakness
Publitio 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 |
CVE4.3
NVDPending
|
| Apr 01, 2025 |
CVE-2025-31798
Publitio: A security weakness
Publitio 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 |
CVE4.3
NVDPending
|