Security readout for executives and security teams
Plain-English summary
Affected WordPress sites may allow anyone on the internet to create an administrator account. That could give an attacker full control of the website, customer-facing content, commerce operations, and accessible data. The source bundle identifies versions through 2.4.37 as vulnerable but does not identify a confirmed fixed version.
Executive priority
Treat as an immediate remediation and compromise-assessment priority for public WordPress sites. Inventory affected installations, reduce exposure, and review administrator accounts now. Do not assume an update is safe until vendor guidance confirms a fixed version.
Technical view
The plugin’s user_filter function lacks required authorization checks (CWE-863). In versions up to and including 2.4.37, an unauthenticated, remote attacker can create an administrator account without user interaction. CVSS 3.1 rates this 9.8 critical, with potentially complete confidentiality, integrity, and availability impact.
Likely exposure
Internet-accessible WordPress installations running and activating version 2.4.37 or earlier are potentially exposed. Prioritize public ecommerce sites because administrative compromise could affect site content, transactions, users, and stored data. Actual exposure requires confirming plugin versions and activation status across the environment.
Exploitation context
The bundle provides no evidence of active exploitation, and the CVE is not listed as KEV. However, the stated conditions are concerning: network access, low complexity, no authentication, and no user interaction. Absence from KEV does not establish that exploitation has not occurred.
Researcher notes
The source bundle attributes the flaw to missing authorization in user_filter and classifies it as CWE-863. Its narrative says all versions through 2.4.37 are affected, but the structured affected entry lists version "0" with default status unaffected. Reconcile this inconsistency against the CVE record and vendor guidance before relying on automated version matching.
Mitigation direction
- Identify every WordPress site running version 2.4.37 or earlier of the affected plugin.
- Check vendor or WordPress guidance for a confirmed fixed release, then update promptly when verified.
- Until a fixed release is confirmed, disable or remove the plugin where operationally feasible.
- Investigate unfamiliar administrator accounts and remove them only after preserving appropriate incident evidence.
- If compromise is suspected, isolate the site and rotate privileged credentials through established incident-response procedures.
Validation and detection
- Confirm the installed plugin version and whether the affected plugin is active on each WordPress site.
- Verify vendor guidance explicitly identifies the deployed replacement version as fixed.
- Review administrator accounts, creation times, and associated activity for unauthorized additions.
- Inspect web, application, and security logs for anomalous activity associated with account creation.
- After remediation, verify unauthenticated users cannot trigger privileged account creation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-10656 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/1f891b68-72c4-4f94-bd49-52576ad710f9?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/excel-like-price-change-for-woocommerce-and-wp-e-commerce-light/trunk/sellingcommander.php#L3725CVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.