Security readout for executives and security teams
Plain-English summary
A WordPress plugin used to manage custom fields could let an attacker change meta field values if they trick an administrator into taking an action. The impact is limited to integrity of stored content or metadata, not direct data theft or server takeover based on the supplied sources.
Executive priority
Treat as a routine but real integrity issue. Prioritize remediation on public or business-critical WordPress sites where content changes could affect trust, SEO, forms, or operational workflows.
Technical view
Custom Field Template for WordPress through version 2.5.1 lacks proper nonce validation in edit_meta_value(), creating a CSRF condition. Attackers need no account, but need administrator interaction. CVSS is 4.3 with low integrity impact and no confidentiality or availability impact stated.
Likely exposure
Exposure is limited to WordPress sites running Custom Field Template version 2.5.1 or older, especially where administrators are logged in and can be targeted by malicious links or pages.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires social engineering an administrator, so risk is lower than unauthenticated direct compromise but still relevant for content integrity.
Researcher notes
The affected-data block in the bundle is sparse, but the narrative states Custom Field Template through 2.5.1 is vulnerable. Avoid claiming active exploitation. Focus validation on version inventory, admin interaction exposure, and whether nonce validation was added in the referenced WordPress changeset.
Mitigation direction
- Inventory WordPress sites for Custom Field Template installations.
- Update or remove versions 2.5.1 and older using vendor guidance.
- Restrict administrator browsing from logged-in WordPress sessions where practical.
- Review WordPress admin hardening and CSRF-aware operational practices.
Validation and detection
- Confirm plugin presence and installed version across WordPress assets.
- Verify affected versions are no longer deployed in production.
- Review recent meta field changes for unexpected modifications.
- Check vendor or WordPress plugin guidance for the fixed release status.
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-2020-36742 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/3444c4b0-4619-482f-8313-d3006aa1e845?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=2368204%40custom-field-template&new=2368204%40custom-field-template&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.