Security readout for executives and security teams
Plain-English summary
CVE-2022-43492 affects the WordPress wpDiscuz comments plugin version 7.4.2. A logged-in low-privilege user, such as a subscriber, may access information they should not be able to access. The available sources rate it medium severity and do not show known active exploitation.
Executive priority
Treat this as a moderate-priority WordPress plugin exposure. It is not described as actively exploited, but public-registration sites should be checked promptly because subscriber access may be enough to trigger the issue.
Technical view
The issue is an authenticated insecure direct object reference in Comments - wpDiscuz 7.4.2, mapped to CWE-639. CVSS 3.1 is 4.3: network reachable, low attack complexity, low privileges required, no user interaction, unchanged scope, and low confidentiality impact only.
Likely exposure
Exposure is limited to WordPress sites running wpDiscuz 7.4.2 where untrusted users can authenticate at subscriber level or above. Sites with public account registration have a higher practical exposure than sites with tightly controlled WordPress accounts.
Exploitation context
The source bundle does not provide exploit details or evidence of exploitation in the wild. CISA KEV status is false. The CVSS vector indicates exploitation requires an authenticated low-privilege account but no victim interaction.
Researcher notes
Sources identify the class and affected version but do not include endpoint-level details, a fixed version, or exploitation evidence. Focus validation on authorization boundaries for authenticated subscriber-level users and avoid assuming integrity or availability impact beyond the published CVSS vector.
Mitigation direction
- Inventory WordPress sites for wpDiscuz version 7.4.2.
- Check wpDiscuz, WordPress.org, and Patchstack guidance for a fixed version or vendor workaround.
- Update the plugin if vendor guidance identifies a corrected release.
- Disable public user registration if it is not operationally required.
- Review subscriber-level accounts and remove unnecessary or suspicious users.
Validation and detection
- Confirm whether wpDiscuz is installed on each WordPress site.
- Record the installed plugin version and flag version 7.4.2.
- Check whether public WordPress registration is enabled.
- Verify only trusted users hold subscriber or higher roles.
- Review vendor advisories before marking remediation complete.
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-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2022-43492 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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.
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:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.