LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47669: WordPress Profile Builder Plugin <= 3.10.3 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Cozmoslabs User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor plugin <= 3.10.3 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites using the Cozmoslabs Profile Builder plugin version 3.10.3 or earlier. It is a CSRF issue, meaning an attacker may need to trick a user into taking an unintended browser action. The listed impact is limited but can affect integrity and availability. Sources do not identify active exploitation.

Executive priority

Treat as a routine but real WordPress plugin remediation item. Prioritize internet-facing or business-critical WordPress sites, especially where user registration or role management matters. Urgency is moderate because exploitation is not confirmed and user interaction is required.

Technical view

CVE-2023-47669 is a CWE-352 CSRF vulnerability in the WordPress profile-builder plugin, reported for versions up to 3.10.3. CVSS 3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, and required user interaction. The source bundle does not describe the vulnerable endpoint, exact action, or fixed version.

Likely exposure

Exposure is likely limited to WordPress installations with Cozmoslabs User Profile Builder / profile-builder version 3.10.3 or earlier enabled.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. CSRF generally depends on a targeted user interacting with attacker-controlled content while authenticated. The specific plugin action affected is not provided.

Researcher notes

Evidence is incomplete. The source bundle identifies CSRF, CVSS, affected plugin, and version ceiling, but not the vulnerable request, affected capability, fixed version, or proof-of-concept status. Avoid assuming impact beyond low integrity and availability effects.

Mitigation direction

  • Inventory WordPress sites for the profile-builder plugin.
  • Confirm whether any installed version is 3.10.3 or earlier.
  • Check Cozmoslabs and Patchstack guidance for the fixed release.
  • Upgrade away from vulnerable versions once vendor guidance is confirmed.
  • Restrict administrative access and review role permissions until updated.

Validation and detection

  • Verify plugin name, package name, and installed version in each WordPress instance.
  • Confirm affected sites are not running version 3.10.3 or earlier.
  • Review vendor advisories for the exact fixed version and remediation notes.
  • Check change logs for unexpected profile, registration, or role-related modifications.
  • Document any compensating controls if immediate upgrade is delayed.
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-2023-47669 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-2023-47669Attack 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
CozmoslabsUser Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editorprofile-builder, 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.