CVE-2025-62091
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-62091 is a Missing Authorization (Broken Access Control) vulnerability in the "Serial Codes Generator and Validator with WooCommerce Support" WordPress plugin developed by Vollstart. It affects all versions up to and including 2.8.2, allowing authenticated users with low privileges (Subscriber level) to perform actions beyond their intended authorization. The vulnerability was reported on October 8, 2025, and publicly disclosed on December 31, 2025, by Patchstack. It carries a CVSS v3.1 base score of 5.4 (Medium) (Patchstack, Red Hat CVE).

Technical details

The root cause is classified as CWE-862 (Missing Authorization), meaning the plugin fails to properly verify whether an authenticated user has the necessary permissions before executing certain privileged actions. This falls under the OWASP Top 10 category A1: Broken Access Control. An attacker with a low-privilege WordPress account (e.g., Subscriber) can exploit this over the network without user interaction or elevated complexity, triggering actions that should be restricted to higher-privileged roles such as administrators. No public proof-of-concept code has been identified at this time (Patchstack).

Impact

Successful exploitation results in limited but meaningful integrity and availability impacts — specifically, low-level unauthorized modifications and minor disruption — with no confidentiality impact according to the CVSS scoring. An authenticated attacker with Subscriber-level access could manipulate serial code data or plugin functionality beyond their intended permissions, potentially disrupting WooCommerce-integrated serial code workflows. The scope is limited to the affected WordPress installation and does not directly enable lateral movement or sensitive data exfiltration (Patchstack).

Exploitability

No active in-the-wild exploitation has been reported, and no exploit code is publicly known. The EPSS score is approximately 0.036%, indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Patchstack notes that while vulnerabilities of this class are sometimes used in mass-exploit campaigns targeting WordPress sites, this specific issue is assessed as low priority with unlikely exploitation impact (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the "Serial Codes Generator and Validator with WooCommerce Support" plugin at version 2.8.2 or earlier using tools like WPScan or by inspecting plugin directories.
  2. Obtain low-privilege access: Register or log in as a Subscriber-level user on the target WordPress site.
  3. Identify unprotected endpoints: Probe plugin-specific AJAX actions or admin-post endpoints that lack proper capability checks, which would normally be restricted to higher-privileged roles.
  4. Send unauthorized request: Craft and submit an authenticated HTTP request (e.g., via AJAX or direct POST) to the vulnerable endpoint, bypassing the missing authorization check to perform privileged actions such as modifying or deleting serial codes.
  5. Achieve objective: Successfully execute the restricted action (e.g., manipulating WooCommerce serial code records) without administrator privileges (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing authenticated POST requests to plugin-specific AJAX endpoints (e.g., wp-admin/admin-ajax.php) from Subscriber-level accounts performing administrative actions outside normal usage patterns.
  • Application Logs: Unexpected modifications to serial code records in the WooCommerce database (e.g., codes being created, deleted, or marked as used) not attributable to administrator activity.
  • Network: Repeated authenticated requests from the same low-privilege user account targeting plugin endpoints in a short timeframe, suggesting automated probing or exploitation.

Mitigation and workarounds

The vendor has released version 2.8.3 of the "Serial Codes Generator and Validator with WooCommerce Support" plugin, which patches this vulnerability. Site administrators should update to version 2.8.3 or later immediately via the WordPress plugin dashboard. If an immediate update is not possible, consider restricting new user registrations or disabling the plugin temporarily until the patch can be applied. Patchstack users can enable auto-update for vulnerable plugins as an additional safeguard (Patchstack).

Community reactions

The vulnerability was discovered and reported by security researcher Jitlada and disclosed through Patchstack's vulnerability disclosure program on December 31, 2025. Patchstack classified it as low priority, noting it is unlikely to be exploited in a high-impact manner. No significant broader media coverage or notable researcher commentary beyond the initial Patchstack disclosure has been identified (Patchstack).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management