CVE-2020-36666: Multiple e-plugins - Subscriber+ Privilege Escalation
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.90% (FIRST EPSS); higher than 59.9% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 27, 2023
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 59th percentile
- CWE
- CWE-269
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| e-plugins | directory pro | cpe:2.3:a:e-plugins:directory_pro |
| e-plugins | final user | cpe:2.3:a:e-plugins:final_user |
| e-plugins | fitness trainer | cpe:2.3:a:e-plugins:fitness_trainer |
| e-plugins | hospital \& doctor directory | cpe:2.3:a:e-plugins:hospital_\&_doctor_directory |
| e-plugins | hotel directory | cpe:2.3:a:e-plugins:hotel_directory |
| e-plugins | institutions directory | cpe:2.3:a:e-plugins:institutions_directory |
| e-plugins | lawyer directory | cpe:2.3:a:e-plugins:lawyer_directory |
| e-plugins | photographer-directory | cpe:2.3:a:e-plugins:photographer-directory |
| e-plugins | producer-retailer | cpe:2.3:a:e-plugins:producer-retailer |
| e-plugins | real estate pro | cpe:2.3:a:e-plugins:real_estate_pro |
| e-plugins | wp membership | cpe:2.3:a:e-plugins:wp_membership |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- e-plugins directory probefore 1.9.5
- e-plugins final userbefore 1.2.2
- e-plugins fitness trainerbefore 1.4.1
- e-plugins hospital & doctor directorybefore 1.3.6
- e-plugins hotel directorybefore 1.3.7
- e-plugins institutions directorybefore 1.3.1
- e-plugins lawyer directorybefore 1.2.9
- e-plugins photographer-directorybefore 1.0.9
- e-plugins producer-retailerall versions
- e-plugins real estate probefore 1.7.1
- e-plugins wp membershipbefore 1.5.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.
Unknown directory-pro
- before 1.9.5affected
Unknown doctor-listing
- before 1.3.6affected
Unknown final-user-wp-frontend-user-profiles
- before 1.2.2affected
Unknown fitness-trainer
- before 1.4.1affected
Unknown Hotel Listing
- before 1.3.7affected
Unknown institutions-directory
- before 1.3.1affected
Unknown lawyer-directory
- before 1.2.9affected
Unknown photographer-directory
- before 1.0.9affected
Unknown producer-retailer
- up to and including TODOaffected
Unknown real-estate-pro
- before 1.7.1affected
Unknown wp-membership
- before 1.5.7affected
Same product
e-plugins: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-66649WordPress Directory Pro plugin <= 2.5.8 - SQL Injection vulnerability37Monitor
- CVE-2026-27396WordPress Directory Pro plugin <= 2.5.6 - Broken Access Control vulnerability29Monitor
- CVE-2025-52748WordPress Directory Pro plugin <= 2.5.5 - Cross Site Scripting (XSS) Vulnerability28Monitor
Published before and after this one in the same product
- Later →CVE-2025-57948Sep 22, 2025 · WordPress Directory Pro Plugin <= 2.5.5 - Cross Site Scripting (XSS) Vulnerability26Monitor
- Later →CVE-2025-64243Dec 16, 2025 · WordPress Directory Pro plugin <= 2.5.6 - Broken Access Control vulnerability17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Omar Badranfinder
- WPScancoordinator
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.