dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-8536

CRITICAL · 9.3 CVSS v4.0 Published 2025-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
A SQL injection vulnerability has been identified in DobryCMS. Improper neutralization of input provided by user into language functionality allows for SQL Injection attacks. This issue affects older branches of this software.

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 · moderate confidence

SQL injection vulnerability in DobryCMS language functionality allows remote attackers to inject malicious SQL queries through unsanitized user input. The lack of proper input validation or parameterized queries in language-related database operations enables unauthenticated attackers to manipulate SQL statements, potentially gaining full database access including sensitive data exfiltration or modification.

MitigationUpgrade to a patched version of DobryCMS. If no patched version exists, implement parameterized queries or prepared statements for all language functionality database operations, and apply input validation/sanitization on user-supplied language parameters.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify if DobryCMS is installed
    Check your web server directories for DobryCMS files (look for 'dobry', 'cms', or language-related PHP files). Search for CMS signature files like index.php, admin, or configuration files containing 'DobryCMS' string.
    Affected if DobryCMS is present in your web environment
  2. Verify language functionality is exposed
    Locate language-related modules or handlers in the DobryCMS installation. Check for URL parameters or form inputs related to language selection (commonly 'lang', 'language', 'locale', or similar). Test if user-supplied language values are accepted without authentication.
    Affected if Language selection parameters accept user input and are used in database queries without authentication
  3. Inspect language database operations for SQL injection vulnerabilities
    Review the source code of language-related PHP files. Search for direct string concatenation in SQL queries using language parameters (e.g., $_GET['lang'], $_POST['language']). Look for queries that insert language values directly into SQL without parameterized queries or escaping functions.
    Affected if Code shows language user input is concatenated directly into SQL queries without prepared statements or escaping
  4. Check database query logs for suspicious patterns
    Review database logs for unusual or malformed SQL queries containing language parameters. Look for SQL metacharacters (' OR '1'='1, UNION SELECT, comment syntax) in language-related database operations. Compare against your expected legitimate language parameter values.
    Affected if Database logs contain SQL injection attempts or unusual queries in language functionality
  5. Test for unauthenticated SQL injection
    If you have a test environment, attempt parameterized language requests with SQL metacharacters (e.g., lang=en' OR '1'='1). Observe application response for SQL errors, unexpected behavior, or data exposure. Only perform on systems you own or have explicit permission to test.
    Affected if Application responds with SQL syntax errors or returns unexpected data when SQL metacharacters are provided in language parameters

Your environment is affected if DobryCMS is running and its language functionality accepts user-supplied input that gets inserted directly into SQL queries without sanitization or parameterized queries.

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

Upgrade to a patched version of DobryCMS. If no patched version exists, implement parameterized queries or prepared statements for all language functionality database operations, and apply input validation/sanitization on user-supplied language parameters.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8536 — 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-2025-8536 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