dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-15070

HIGH · 8.8 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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().

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Salon Booking System WordPress plugin fails to validate nonces on the setCustomText function, allowing unauthenticated attackers to forge administrative requests via CSRF. Although sanitize_text_field() is applied to the POST 'value' parameter, it does not escape PHP special characters (single quotes, parentheses, semicolons, $, and []), enabling attackers to break out of the string literal and inject arbitrary PHP code. This code is written via file_put_contents() to the web-accessible translate-constants.php file, achieving remote code execution.

MitigationUpdate to a patched version when released. Until then, enforce CSRF protections via anti-CSRF tokens on all state-changing actions and implement proper PHP escaping (addslashes or similar) before file写入, or restrict file_put_contents access entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Salon Booking System plugin is installed
    Check your WordPress plugins directory or use WP CLI: wp plugin list --name='salon-booking-system' to list the plugin and its current version
    Affected if Plugin is installed and version cannot be confirmed as patched
  2. Check for the translate-constants.php file
    Look for the file translate-constants.php in the plugin directory (typically wp-content/plugins/salon-booking-system/) or search your web root for this filename using: find /path/to/webroot -name 'translate-constants.php'
    Affected if The file exists in a web-accessible directory
  3. Inspect translate-constants.php for injected code
    Read the contents of translate-constants.php and look for suspicious PHP code patterns such as eval(), base64_decode(), shell_exec(), system(), or unusual string assignments containing $, (), ;, or []
    Affected if The file contains any PHP code that was not intentionally added by administrators
  4. Test setCustomText function for CSRF vulnerability
    Review the plugin source code for the setCustomText function and verify that a nonce validation check is performed before processing the 'value' POST parameter
    Affected if The function lacks nonce verification or the nonce check can be bypassed
  5. Check for unauthorized changes to PHP files
    Compare translate-constants.php with any known clean backup, or check file modification timestamps to identify recent unauthorized changes
    Affected if The file was modified recently or differs from expected content

You are affected if the Salon Booking System plugin is installed, the translate-constants.php file exists with unexpected PHP content, and the setCustomText function lacks proper nonce validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version when released. Until then, enforce CSRF protections via anti-CSRF tokens on all state-changing actions and implement proper PHP escaping (addslashes or similar) before file写入, or restrict file_put_contents access entirely.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation5.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,260
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15070 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data