Odyssey CMS up to 10.34 reCAPTCHA odyssey_contact_form.php g-recaptcha-response key management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Odyssey CMS up to 10.34. This issue affects some unknown processing of the file /modules/odyssey_contact_form/odyssey_contact_form.php of the component reCAPTCHA Handler. The manipulation of the argument g-recaptcha-response results in key management. This vulnerability is reported as CVE-2025-2220. The attack requires a local approach. Moreover, an exploit is present. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in Odyssey CMS up to 10.34. It has been classified as problematic. Affected is an unknown function of the file /modules/odyssey_contact_form/odyssey_contact_form.php of the component reCAPTCHA Handler. The manipulation of the argument g-recaptcha-response with an unknown input leads to a key management vulnerability. CWE is classifying the issue as CWE-320. This is going to have an impact on confidentiality.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2025-2220. The exploitability is told to be easy. The attack needs to be approached locally. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1600.001.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way. By approaching the search of inurl:modules/odyssey_contact_form/odyssey_contact_form.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 10.0
- 10.1
- 10.2
- 10.3
- 10.4
- 10.5
- 10.6
- 10.7
- 10.8
- 10.9
- 10.10
- 10.11
- 10.12
- 10.13
- 10.14
- 10.15
- 10.16
- 10.17
- 10.18
- 10.19
- 10.20
- 10.21
- 10.22
- 10.23
- 10.24
- 10.25
- 10.26
- 10.27
- 10.28
- 10.29
- 10.30
- 10.31
- 10.32
- 10.33
- 10.34
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.1
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 3.3
CNA Vector: 🔍
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: Key managementCWE: CWE-320
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
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
03/11/2025 🔍03/11/2025 🔍
03/12/2025 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2025-2220 (🔍)
GCVE (CVE): GCVE-0-2025-2220
GCVE (VulDB): GCVE-100-299292
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/11/2025 16:23Updated: 03/12/2025 12:12
Changes: 03/11/2025 16:23 (58), 03/12/2025 12:12 (30)
Complete: 🔍
Submitter: secuserx
Cache ID: 216::103
Submit
Accepted
- Submit #512367: Odyssey CMS 10.35 Use of Hard-coded, Security-relevant Constants (by secuserx)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.