Security readout for executives and security teams
Plain-English summary
A vulnerable WordPress plugin can let an outside attacker abuse a logged-in administrator’s browser to make site changes. The reported impact includes adding pages or replacing site content with malicious JavaScript. This is a business risk because it can affect public website integrity, visitors, and brand trust.
Executive priority
Treat this as high priority for any WordPress estate using the plugin. The issue can directly affect public site integrity and visitor safety, but requires administrator interaction and has no cited active exploitation in the provided sources.
Technical view
WP Lead Plus X through version 0.99 lacks proper nonce validation on several administrative functions, creating a CSRF vulnerability. An unauthenticated attacker must trick a WordPress administrator into performing an action, then the forged request may execute administrative changes. CVSS 3.1 is 8.3 high, CWE-352.
Likely exposure
Internet-facing WordPress sites running WP Lead Plus X version 0.99 or earlier. Exposure is most relevant where administrators remain logged into WordPress while browsing email or external websites. The bundle does not identify non-WordPress products as affected.
Exploitation context
The source bundle does not show CISA KEV status or confirmed active exploitation. Exploitation requires administrator interaction, but no attacker account is required. Potential outcomes include unauthorized page creation and malicious script placement in site content.
Researcher notes
The core weakness is missing or incorrect CSRF nonce validation across several functions. Validate exposure by version and plugin presence, not by product name alone. Evidence in the bundle supports high severity and interaction-based exploitation, but does not provide a specific fixed version.
Mitigation direction
- Inventory WordPress sites for WP Lead Plus X and record installed versions.
- Remove the plugin if it is unused or unsupported.
- For versions up to 0.99, follow WordPress.org or vendor remediation guidance.
- Review affected sites for unauthorized pages or injected JavaScript.
- Limit administrator browsing while logged into WordPress.
Validation and detection
- Confirm whether WP Lead Plus X is installed on each WordPress site.
- Verify installed versions are not within the vulnerable range.
- Review recent page and content changes for unauthorized edits.
- Check plugin guidance from Wordfence and WordPress.org before closing remediation.
- Confirm administrator accounts have not made unexplained content changes.
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-36839 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
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H
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:L/I:H/A:H2.85.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ddb97db0-cbf3-42be-a5c7-12fc2a2bc9e8?source=cveCVE reference
- https://www.wordfence.com/blog/2020/04/critical-vulnerabilities-in-the-wp-lead-plus-x-wordpress-plugin/CVE reference
- https://wordpress.org/plugins/free-sales-funnel-squeeze-pages-landing-page-builder-templates-make/#developersCVE 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.