What is the CVSS score of CVE-2020-35773?

CVE-2020-35773 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.0%.

Is there a public PoC exploit available for CVE-2020-35773?

Yes, a public proof-of-concept exploit is available for CVE-2020-35773. Prioritise patching immediately. EPSS: 1.0%.

Is there a patch available for CVE-2020-35773?

Yes, a patch is available for CVE-2020-35773. Update the affected software to the latest version immediately.

Site Offline CVE-2020-35773

HIGH

Cross-Site Request Forgery (CSRF) (CWE-352)

2020-12-29 cve@mitre.org

WordPress CSRF Site Offline

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Dec 29, 2020 - 18:15 nvd

HIGH 8.8

DescriptionNVD

The site-offline plugin before 1.4.4 for WordPress lacks certain wp_create_nonce and wp_verify_nonce calls, aka CSRF.

AnalysisAI

The site-offline plugin before 1.4.4 for WordPress lacks certain wp_create_nonce and wp_verify_nonce calls, aka CSRF. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Cross-Site Request Forgery (CSRF) (CWE-352), which allows attackers to trick authenticated users into performing unintended actions. The site-offline plugin before 1.4.4 for WordPress lacks certain wp_create_nonce and wp_verify_nonce calls, aka CSRF. Affected products include: Freehtmldesigns Site Offline. Version information: before 1.4.4.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Implement anti-CSRF tokens, validate Origin/Referer headers, use SameSite cookie attribute.