Softaculous PageLayer Plugin up to 2.0.8 on WordPress exposure of sensitive system information to an unauthorized control sphere
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Softaculous PageLayer Plugin up to 2.0.8 on WordPress. This affects an unknown part. Executing a manipulation can lead to exposure of sensitive system information to an unauthorized control sphere. This vulnerability is registered as CVE-2026-39469. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as problematic was found in Softaculous PageLayer Plugin up to 2.0.8 on WordPress. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a exposure of sensitive system information to an unauthorized control sphere vulnerability. The CWE definition for the vulnerability is CWE-497. The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. As an impact it is known to affect confidentiality. CVE summarizes:
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Softaculous PageLayer pagelayer allows Retrieve Embedded Sensitive Data.This issue affects PageLayer: from n/a through <= 2.0.8.
The weakness was published by Trương Hữu Phúc. The advisory is available at patchstack.com. This vulnerability was named CVE-2026-39469 since 04/07/2026. The exploitation appears to be easy. The attack can be initiated remotely. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Exposure of sensitive system information to an unauthorized control sphereCWE: CWE-497
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/07/2026 CVE reserved04/08/2026 Advisory disclosed
04/08/2026 VulDB entry created
04/08/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Trương Hữu Phúc
Status: Not defined
CVE: CVE-2026-39469 (🔒)
GCVE (CVE): GCVE-0-2026-39469
GCVE (VulDB): GCVE-100-356050
Entry
Created: 04/08/2026 11:16Changes: 04/08/2026 11:16 (54)
Complete: 🔍
Cache ID: 216:E82:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.