Skip to content
WatchlistMedium

CVE-2020-28976Canto SSRF

The Canto plugin 1.3.0 for WordPress contains a blind SSRF vulnerability.

Published Nov 30, 2020 · Updated Nov 21, 2024 · Also known as 5781420d-b1e0-435f-8bf2-193cc7b095ed, WORDFENCE-5781420d-b1e0-435f-8bf2-193cc7b095ed

Key Facts

Routine patching
  • CVE-2020-28976 is a medium-severity vulnerability (CVSS 5.3 v3.1) affecting Canto.
  • It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
  • EPSS estimates a 28% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Canto 2.0.1.
  • Brandefense priority: routine patching, as no exploitation is known and its severity is moderate or low.

Scores

CVSS v3.1

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS (30-day exploit likelihood)

28%

Higher than 98.0% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

36/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

1

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Description

The Canto plugin 1.3.0 for WordPress contains a blind SSRF vulnerability. It allows an unauthenticated attacker can make a request to any internal and external server via /includes/lib/detail.php?subdomain=SSRF.

Affected Products

2 affected entries in total
ProductAffected versionsFixed in
CantoCanto1.3.02.0.1

Patched Releases

Canto

2.0.1

Timeline

  1. Publicly disclosed

    Nov 30, 2020

  2. Last updated

    Nov 21, 2024

Weakness Type

  • CWE-918 Server-Side Request Forgery (SSRF)

FAQ

Common Questions.

Is CVE-2020-28976 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.