CVE-2025-68567

My auctions allegro <= 3.6.33 - Cross-Site Request Forgery

2025-12-17 00:00
Muhammad Nur Ibnu Hubab

Strategic Overview

Status
Patched in 3.6.34
Affected Plugin
My auctions allegro
Affected Version
<= 3.6.33
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-68567
View all My auctions allegro vulnerabilities

At a glance

CVE-2025-68567 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the My auctions allegro WordPress plugin, affecting versions <= 3.6.33. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.6.34; sites on affected versions should update now. Disclosed December 2025, reported by Muhammad Nur Ibnu Hubab.

Vulnerability Overview

The My auctions allegro plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.6.33. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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.

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

Reaching this weakness in My auctions allegro <= 3.6.33 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 My auctions allegro the fix is 3.6.34: builds <= 3.6.33 are affected, anything from 3.6.34 onward is not.

Remediation

Update to version 3.6.34, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-68567https://www.wordfence.com/threat-intel/vulnerabilities/id/e1120811-e0da-4dec-9723-0fdbd86efe67https://nvd.nist.gov/vuln/detail/CVE-2025-68567

Related records

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