CVE-2023-25448

Archivist – Custom Archive Templates <= 1.7.4 - Cross-Site Request Forgery

2023-02-15 00:00
yuyudhn

Strategic Overview

Status
Patched in 1.7.5
Affected Version
<= 1.7.4
CVSS
7.1High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-25448
View all Archivist – Custom Archive Templates vulnerabilities

At a glance

CVE-2023-25448 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Archivist WordPress plugin, affecting versions <= 1.7.4. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.7.5; sites on affected versions should update now. Disclosed February 2023, reported by yuyudhn.

Vulnerability Overview

The Archivist – Custom Archive Templates plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.7.4. This is due to missing or incorrect nonce validation on the 'settings_page' function. This makes it possible for unauthenticated attackers to modify plugin settings via a 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 integrity.

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

Archivist <= 1.7.4 carries this weakness at settings_page, and reaching it 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 Archivist the fix is 1.7.5: builds <= 1.7.4 are affected, anything from 1.7.5 onward is not.

Remediation

Update to version 1.7.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Archivist: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Archivist 1.7.5 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