ThemeRuby Easy Post Submission Plugin up to 1.7.0 on WordPress insertion of sensitive information into sent data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in ThemeRuby Easy Post Submission Plugin up to 1.7.0 on WordPress. This issue affects some unknown processing. The manipulation leads to insertion of sensitive information into sent data. This vulnerability is uniquely identified as CVE-2025-62062. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in ThemeRuby Easy Post Submission Plugin up to 1.7.0 on WordPress. It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a insertion of sensitive information into sent data vulnerability. Using CWE to declare the problem leads to CWE-201. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. Impacted is confidentiality. The summary by CVE is:
Insertion of Sensitive Information Into Sent Data vulnerability in ThemeRuby Easy Post Submission easy-post-submission allows Retrieve Embedded Sensitive Data.This issue affects Easy Post Submission: from n/a through <= 1.7.0.
The weakness was disclosed by Nabil Irawan. The advisory is shared at vdp.patchstack.com. The identification of this vulnerability is CVE-2025-62062 since 10/07/2025. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/22/2025). MITRE ATT&CK project uses the attack technique T1592 for this issue.
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 the best quality for vulnerability data then you always have to consider 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: Insertion of sensitive information into sent dataCWE: CWE-201 / CWE-200 / CWE-284
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
10/07/2025 CVE reserved10/22/2025 Advisory disclosed
10/22/2025 VulDB entry created
10/22/2025 VulDB entry last update
Sources
Advisory: vdp.patchstack.comResearcher: Nabil Irawan
Status: Not defined
CVE: CVE-2025-62062 (🔒)
GCVE (CVE): GCVE-0-2025-62062
GCVE (VulDB): GCVE-100-329597
Entry
Created: 10/22/2025 20:17Changes: 10/22/2025 20:17 (54)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.