Cuppa CMS 1.0 /Configuration.php email_outgoing code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Cuppa CMS 1.0. The affected element is an unknown function of the file /Configuration.php. This manipulation of the argument email_outgoing causes an unknown weakness. The identification of this vulnerability is CVE-2023-39681. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Cuppa CMS 1.0 (Content Management System). It has been declared as critical. Affected by this vulnerability is some unknown functionality of the file /Configuration.php. The manipulation of the argument email_outgoing with an unknown input leads to a unknown weakness. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Cuppa CMS v1.0 was discovered to contain a remote code execution (RCE) vulnerability via the email_outgoing parameter at /Configuration.php. This vulnerability is triggered via a crafted payload.
The weakness was shared 09/06/2023. The advisory is shared at github.com. This vulnerability is known as CVE-2023-39681 since 08/07/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
By approaching the search of inurl:Configuration.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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-43382). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD 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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
08/07/2023 🔍09/06/2023 🔍
09/06/2023 🔍
01/25/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-39681 (🔍)
GCVE (CVE): GCVE-0-2023-39681
GCVE (VulDB): GCVE-100-238849
EUVD: 🔍
Entry
Created: 09/06/2023 07:28Updated: 01/25/2026 18:29
Changes: 09/06/2023 07:28 (38), 10/01/2023 09:10 (12), 01/25/2026 18:29 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.