LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41633: WordPress Community by PeepSo Plugin <= 6.0.2.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in PeepSo Community by PeepSo – Social Network, Membership, Registration, User Profiles plugin <= 6.0.2.0 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-41633 is a CSRF issue in the WordPress Community by PeepSo plugin, affecting versions up to 6.0.2.0. A successful attack could cause limited integrity or availability impact through a user’s browser. The available sources rate it medium severity and do not show active exploitation.

Executive priority

Treat this as a moderate-priority WordPress plugin exposure. It is not currently supported by evidence of active exploitation, but internet-facing community sites should be checked and updated because CSRF can cause unauthorized actions through legitimate user sessions.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in peepso-core, the Community by PeepSo WordPress plugin. CVSS 3.1 is 5.4 with network access, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact. Source data does not identify the vulnerable endpoint or a fixed version.

Likely exposure

Exposure is most likely on WordPress sites running Community by PeepSo / peepso-core version 6.0.2.0 or earlier. Business impact depends on which forged actions the affected plugin permits and the privileges of the targeted user session.

Exploitation context

The source bundle does not indicate CISA KEV listing, active exploitation, public exploit code, or weaponized campaigns. Exploitation would require user interaction consistent with CSRF, where a victim’s browser is induced to send an unintended request.

Researcher notes

Evidence is limited to the CVE record and Patchstack database reference. The public bundle does not name affected routes, nonce failures, proof-of-concept details, exploit maturity, or a confirmed patched version. Avoid assuming impact beyond low integrity and low availability from the CVSS vector.

Mitigation direction

  • Inventory WordPress sites using Community by PeepSo / peepso-core.
  • Check vendor or Patchstack guidance for a fixed release and update accordingly.
  • Prioritize sites running version 6.0.2.0 or earlier.
  • Temporarily disable the plugin on critical sites if no supported update is available.
  • Review WordPress user privileges to reduce impact from forged actions.

Validation and detection

  • Confirm installed peepso-core version on each WordPress site.
  • Verify whether the installed version is 6.0.2.0 or earlier.
  • Check vendor advisory status for the installed version.
  • Review access logs for unusual plugin-related state-changing requests.
  • Document affected sites, remediation owner, and update status.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookup
cve · low confidence lookup

CVE-2022-41633 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-41633Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PeepSoCommunity by PeepSo – Social Network, Membership, Registration, User Profilespeepso-core, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.