Security readout for executives and security teams
Plain-English summary
This is a medium-risk WordPress plugin issue. If a site administrator is logged in and is tricked into taking an action, an attacker may cause the Staff Directory Plugin to save custom fields without proper request verification. The expected impact is limited data integrity change, not direct data theft or service outage.
Executive priority
Treat this as a routine but real website integrity issue. Prioritize if the plugin is installed on public-facing WordPress sites or if staff directory content affects customer trust, compliance pages, or business contact routing.
Technical view
CVE-2021-4397 is a CWE-352 CSRF weakness in Staff Directory Plugin for WordPress through version 3.6. The source bundle identifies missing or incorrect nonce validation in saveCustomFields(). The CVSS 3.1 score is 4.3, with network reachability, low attack complexity, no privileges, required user interaction, and low integrity impact.
Likely exposure
Exposure is limited to WordPress sites running Staff Directory Plugin versions up to and including 3.6. Successful abuse requires a logged-in administrator to interact with attacker-controlled content. The affected-product metadata in the bundle is inconsistent, so confirm against vendor and plugin repository records.
Exploitation context
The bundle does not cite CISA KEV listing or active exploitation. The described attack depends on social engineering and an authenticated administrator session. Sources support possible unauthorized custom-field changes, not remote code execution, credential theft, or availability loss.
Researcher notes
Primary evidence comes from the CVE description, Wordfence entry, Nintechnet CSRF research references, and a WordPress plugin Trac changeset. The bundle does not provide exploit-in-the-wild evidence or a clearly named fixed version. The affected-product version field appears inconsistent with the narrative affected range.
Mitigation direction
- Inventory WordPress sites for Staff Directory Plugin and confirm installed versions.
- Update to a vendor-supported release newer than the affected range if available.
- If no fixed release is available, disable or replace the plugin until vendor guidance is clear.
- Limit administrator browsing from logged-in WordPress sessions, especially from untrusted links.
- Review vendor, Wordfence, and WordPress Trac guidance before accepting residual risk.
Validation and detection
- Check WordPress plugin inventory for Staff Directory Plugin versions up to 3.6.
- Confirm whether saveCustomFields() has nonce validation in the installed plugin code.
- Review WordPress Trac changeset 2548539 for relevant security changes.
- Look for unexpected staff directory custom-field changes in site administration history or backups.
- Verify administrators cannot change custom fields through unverified cross-origin requests in staging.
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-2021-4397 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/5971447d-0634-49a5-91d0-c4f0c0825a86?source=cveCVE reference
- https://blog.nintechnet.com/25-wordpress-plugins-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/more-wordpress-plugins-and-themes-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-3/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-2/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-1/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-5/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-4/CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2548539%40staff-directory-pro&new=2548539%40staff-directory-pro&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.