Security readout for executives and security teams
Plain-English summary
CVE-2020-36875 is a critical remote code execution issue in the AccessAlly WordPress plugin before version 3.3.2. An unauthenticated attacker could make the website run attacker-supplied PHP through the Login Widget. Compromise could allow full control of the WordPress site under the web server account.
Executive priority
Prioritize immediately for any internet-facing WordPress site using AccessAlly before 3.3.2. The business risk is site takeover, data exposure, malware placement, and reputational damage. No active exploitation is proven in the supplied sources, but the technical barrier is low.
Technical view
The vulnerability is CWE-94 code injection. AccessAlly processes the login_error parameter as PHP code in the Login Widget, enabling unauthenticated arbitrary PHP execution. The CVSS 4.0 score is 9.3, reflecting network access, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is likely limited to WordPress sites running AccessAlly versions earlier than 3.3.2, especially where the Login Widget is reachable. The source bundle’s affected-version metadata is inconsistent, but the description and advisories identify versions prior to 3.3.2 as vulnerable.
Exploitation context
The WPScan reference is tagged as exploit, indicating public exploit information exists. The provided sources do not show CISA KEV listing or active exploitation evidence. Treat internet-facing affected WordPress sites as urgent because exploitation requires no authentication or user interaction.
Researcher notes
Sources identify unauthenticated PHP execution through login_error handling in the AccessAlly Login Widget. Avoid assuming all AccessAlly versions are affected; the evidence points to versions before 3.3.2. The CVE record’s structured affected field appears incomplete or inconsistent with the narrative.
Mitigation direction
- Upgrade AccessAlly to version 3.3.2 or later.
- If upgrade status is unclear, check current AccessAlly vendor guidance.
- Restrict exposure of affected WordPress sites until patched.
- Review administrative access and site integrity after remediation.
Validation and detection
- Inventory WordPress sites using the AccessAlly plugin.
- Confirm the installed AccessAlly version is 3.3.2 or later.
- Identify whether the Login Widget is exposed publicly.
- Review web and WordPress logs for suspicious unauthenticated requests.
- Verify the vendor release notes or advisory for applied fixes.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-36875 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
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://accessally.com/software-release/accessally-3-3-2/CVE reference · vendor-advisory, patch
- https://wpscan.com/vulnerability/c644de6d-098d-4889-b75d-53fd2b89ff4d/CVE reference · third-party-advisory, exploit
- https://www.vulncheck.com/advisories/accessally-unauthenticated-arbitrary-php-code-executionCVE reference · third-party-advisory
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.