Security readout for executives and security teams
Plain-English summary
CVE-2026-1644 affects the WP Frontend Profile WordPress plugin through version 1.3.8. An attacker could trick an administrator into clicking a crafted link that approves or rejects user registrations without authorization. Business impact is limited but real: account onboarding decisions can be manipulated on affected sites.
Executive priority
Handle in the normal vulnerability remediation cycle unless the site depends heavily on controlled user registration. Prioritize public-facing WordPress sites with active registration and multiple administrators who may receive external links.
Technical view
The plugin lacks nonce validation in the update_action function, creating a CSRF flaw classified as CWE-352. The CVSS 3.1 score is 4.3. Exploitation requires administrator interaction and affects integrity only; the cited record reports no confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress sites running WP Frontend Profile versions up to and including 1.3.8, especially sites using registration approval workflows. The provided affected-product metadata is inconsistent, so validate against installed plugin version and vendor records.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not listed as KEV. An attacker does not need authentication, but must induce an administrator to perform an action such as clicking a link.
Researcher notes
The key condition is missing nonce validation on update_action. The provided references include Wordfence, plugin source at tag 1.3.8, trunk source, and a WordPress Trac changeset. The bundle does not clearly name a fixed version, so remediation status should be verified upstream.
Mitigation direction
- Identify all WordPress sites using WP Frontend Profile.
- Check vendor or WordPress plugin repository guidance for a fixed release.
- Update the plugin if a fixed version is available.
- Restrict administrator browsing and email-clicking exposure where practical.
- Review user registration approval workflows for unexpected changes.
Validation and detection
- Confirm whether WP Frontend Profile is installed.
- Record the installed plugin version on each WordPress site.
- Treat versions 1.3.8 and earlier as affected per the CVE description.
- Review the update_action handling for nonce validation if source review is feasible.
- Check logs or audit records for unexpected approval or rejection events.
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-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 lookupCVE-2026-1644 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:N/UI:R/S:U/C:N/I:L/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:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/74b186fd-5825-4a20-829b-6b8a5ddbe853?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/wp-front-end-profile/tags/1.3.8/functions/wpfep-functions.php#L987CVE reference
- https://plugins.trac.wordpress.org/browser/wp-front-end-profile/trunk/functions/wpfep-functions.php#L987CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3466608%40wp-front-end-profile&new=3466608%40wp-front-end-profile&sfp_email=&sfph_mail=CVE reference
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.
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.