o2oe E-Invoice App Malaysia Plugin up to 1.1.0 on WordPress information expsure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in o2oe E-Invoice App Malaysia Plugin up to 1.1.0 on WordPress. This impacts an unknown function. Performing a manipulation results in information expsure. This vulnerability is reported as CVE-2025-68988. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic has been found in o2oe E-Invoice App Malaysia Plugin up to 1.1.0 on WordPress. This affects an unknown functionality. The manipulation with an unknown input leads to a information expsure vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality. The summary by CVE is:
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in o2oe E-Invoice App Malaysia einvoiceapp-malaysia allows Retrieve Embedded Sensitive Data.This issue affects E-Invoice App Malaysia: from n/a through <= 1.1.0.
The weakness was disclosed by Rapid0nion. It is possible to read the advisory at vdp.patchstack.com. This vulnerability is uniquely identified as CVE-2025-68988 since 12/29/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-205748). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: Information expsureCWE: 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
12/29/2025 CVE reserved12/30/2025 Advisory disclosed
12/30/2025 VulDB entry created
12/31/2025 VulDB entry last update
Sources
Advisory: vdp.patchstack.comResearcher: Rapid0nion
Status: Not defined
CVE: CVE-2025-68988 (🔒)
GCVE (CVE): GCVE-0-2025-68988
GCVE (VulDB): GCVE-100-338787
EUVD: 🔒
Entry
Created: 12/30/2025 15:30Updated: 12/31/2025 01:57
Changes: 12/30/2025 15:30 (54), 12/31/2025 01:57 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.