LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36666: Multiple e-plugins - Subscriber+ Privilege Escalation

The directory-pro WordPress plugin before 1.9.5, final-user-wp-frontend-user-profiles WordPress plugin before 1.2.2, producer-retailer WordPress plugin through TODO, photographer-directory WordPress plugin before 1.0.9, real-estate-pro WordPress plugin before 1.7.1, institutions-directory WordPress plugin before 1.3.1, lawyer-directory WordPress plugin before 1.2.9, doctor-listing WordPress plugin before 1.3.6, Hotel Listing WordPress plugin before 1.3.7, fitness-trainer WordPress plugin before 1.4.1, wp-membership WordPress plugin before 1.5.7, sold by the same developer (e-plugins), do not implementing any security measures in some AJAX calls. For example in the file plugin.php, the function iv_directories_update_profile_setting() uses update_user_meta with any data provided by the ajax call, which can be used to give the logged in user admin capabilities. Since the plugins allow user registration via a custom form (even if the blog does not allow users to register) it makes any site using it vulnerable.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A normal account on an affected WordPress site could potentially promote itself to administrator through plugin profile-update behavior. Because these plugins can allow custom user registration even when WordPress registration is disabled, exposure may exist wherever the plugin registration flow is reachable.

Executive priority

Treat this as high priority for WordPress sites running any affected e-plugins product. The business risk is full site compromise from a low-privilege account, especially where public registration is possible.

Technical view

CVE-2020-36666 is a CWE-269 privilege escalation affecting multiple e-plugins WordPress plugins. Some AJAX calls lack security measures; one cited function uses update_user_meta with user-supplied AJAX data, potentially letting an authenticated low-privilege user assign administrator capabilities. CVSS 3.1 score is 8.8.

Likely exposure

WordPress sites using the listed e-plugins versions before their fixed releases are the primary exposure. producer-retailer is listed as affected through an unspecified version, so its fixed status is unclear in the supplied evidence.

Exploitation context

The CVE is not listed as KEV, and the supplied bundle does not prove active exploitation. WPScan is cited as an exploit-tagged vulnerability entry, indicating public technical awareness, but not confirmed in-the-wild activity.

Researcher notes

Evidence centers on missing security controls in AJAX handlers and unsafe update_user_meta usage. Fixed versions are provided for most plugins, but producer-retailer has incomplete version data. Do not assume active exploitation from the supplied sources.

Mitigation direction

  • Upgrade affected plugins to the fixed versions named in the CVE record.
  • Disable or remove affected plugins when a safe version is unavailable.
  • For producer-retailer, check vendor or WPScan guidance because the fixed version is unspecified.
  • Audit administrator users and capability-related user metadata for unexpected changes.
  • Review whether plugin-based public registration is enabled or reachable.

Validation and detection

  • Inventory installed WordPress plugins and compare versions against the CVE’s affected list.
  • Confirm profile-setting AJAX handlers require authorization checks and CSRF protection.
  • Audit wp_usermeta for unexpected administrator capability assignments.
  • Review logs for suspicious profile-setting AJAX activity by low-privilege users.
  • Confirm no affected plugin registration flow is unintentionally public.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-36666 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2020-36666Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknowndirectory-pro0unaffected
Unknownfinal-user-wp-frontend-user-profiles0unaffected
Unknownproducer-retailer0affected
Unknownphotographer-directory0unaffected
Unknownreal-estate-pro0unaffected
Unknowninstitutions-directory0unaffected
Unknownlawyer-directory0unaffected
Unknowndoctor-listing0unaffected
UnknownHotel Listing0unaffected
Unknownfitness-trainer0unaffected
Unknownwp-membership0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.