wordpresschef Salon Booking System Plugin up to 10.30.32 Admin Interface translate-constants.php setCustomText Value cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 2.43 |
Summary
A vulnerability marked as problematic has been reported in wordpresschef Salon Booking System Plugin up to 10.30.32. This issue affects the function setCustomText of the file translate-constants.php of the component Admin Interface. The manipulation of the argument Value leads to cross-site request forgery.
This vulnerability is documented as CVE-2026-15070. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in wordpresschef Salon Booking System Plugin up to 10.30.32. This issue affects the function setCustomText of the file translate-constants.php of the component Admin Interface. The manipulation of the argument value with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:
The Salon Booking System – Free Version plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 10.30.32. This is due to missing or incorrect nonce validation on the setCustomText function. This makes it possible for unauthenticated attackers to inject arbitrary PHP code into the web-accessible translate-constants.php file within the plugin directory, enabling remote code execution on the server via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. sanitize_text_field() is applied to the POST 'value' parameter but does not neutralize the characters — single quotes, parentheses, semicolons, $, and [] — required to break out of the PHP string literal into which the value is interpolated before being written to disk via file_put_contents().
The advisory is shared at wordfence.com. The identification of this vulnerability is CVE-2026-15070 since 07/08/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
By approaching the search of inurl:translate-constants.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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 10.30.0
- 10.30.1
- 10.30.2
- 10.30.3
- 10.30.4
- 10.30.5
- 10.30.6
- 10.30.7
- 10.30.8
- 10.30.9
- 10.30.10
- 10.30.11
- 10.30.12
- 10.30.13
- 10.30.14
- 10.30.15
- 10.30.16
- 10.30.17
- 10.30.18
- 10.30.19
- 10.30.20
- 10.30.21
- 10.30.22
- 10.30.23
- 10.30.24
- 10.30.25
- 10.30.26
- 10.30.27
- 10.30.28
- 10.30.29
- 10.30.30
- 10.30.31
- 10.30.32
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
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
07/08/2026 CVE reserved07/10/2026 Advisory disclosed
07/10/2026 VulDB entry created
07/10/2026 VulDB entry last update
Sources
Advisory: wordfence.comStatus: Not defined
CVE: CVE-2026-15070 (🔒)
GCVE (CVE): GCVE-0-2026-15070
GCVE (VulDB): GCVE-100-377381
Entry
Created: 07/10/2026 05:59Changes: 07/10/2026 05:59 (56)
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.