CVE-2022-3427

Corner Ad <= 1.0.56 - Cross-Site Request Forgery

2022-09-09 00:00
Marco Wotschka

Strategic Overview

Status
Patched in 1.0.57
Affected Plugin
Corner Ad
Affected Version
<= 1.0.56
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-3427
View all Corner Ad vulnerabilities

At a glance

CVE-2022-3427 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Corner Ad WordPress plugin, affecting versions <= 1.0.56. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.0.57; sites on affected versions should update now. Disclosed September 2022, reported by Marco Wotschka.

Vulnerability Overview

The Corner Ad plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.0.56. This is due to missing or incorrect nonce validation on its corner_ad_settings_page function. This makes it possible for unauthenticated attackers to trigger the deletion of ads via forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in Corner Ad <= 1.0.56 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Corner Ad the fix is 1.0.57: builds <= 1.0.56 are affected, anything from 1.0.57 onward is not.

Remediation

Update to version 1.0.57, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Corner Ad: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Corner Ad 1.0.57 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C