dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-0422

HIGH · 8.6 CVSS v4.0 Published 2025-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable 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
An authenticated user in the "bestinformed Web" application can execute commands on the underlying server running the application. (Remote Code Execution) For this, the user must be able to create "ScriptVars" with the type „script" and preview them by, for example, creating a new "Info". By default, admin users have those permissions, but with the granular permission system, those permissions may be assigned to other users. An attacker is able to execute commands on the server running the "bestinformed Web" application if an account with the correct permissions was compromised before.

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

Authenticated users in bestinformed Web with permissions to create ScriptVars of type 'script' can achieve remote code execution by creating a ScriptVar and previewing it (e.g., through creating a new Info). The vulnerability requires prior compromise of an account with the necessary permissions.

MitigationRestrict or disable the ability to create ScriptVars with type 'script' to only trusted administrators, review the granular permission assignments, and if possible implement input sanitization to prevent command execution.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/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 bestinformed Web installation
    Locate the bestinformed application files or check running services on the server hosting the web application. Common locations include /opt/bestinformed, /var/www/bestinformed, or check for bestinformed processes and services.
    Affected if bestinformed Web software is present on the system
  2. Determine installed version
    Check version files in the installation directory, such as version.txt, info.json, or the configuration/config.php file. Alternatively, query the application's built-in about or system info page if available.
    Affected if The installed version matches or predates the vulnerable version range for CVE-2025-0422 (verify against vendor's official vulnerability disclosure)
  3. Verify ScriptVars module is enabled
    Access the administration panel and navigate to the configuration or modules section. Look for ScriptVars or Script Variables settings. Check configuration files (e.g., config.xml, settings.php) for any ScriptVars-related entries set to enabled.
    Affected if The ScriptVars feature is enabled and accessible to users
  4. Review ScriptVars creation permissions
    In the admin panel, go to User Management or Permissions settings. Identify roles or users that have permission to create ScriptVars with type 'script'. Look for permissions labeled as 'Create ScriptVars', 'ScriptVars - script type', or similar.
    Affected if Non-admin or untrusted user accounts have permission to create ScriptVars of type 'script'
  5. Audit existing ScriptVars entries
    Query the database or access the ScriptVars management interface to list all ScriptVars entries. Check the 'type' field to identify any entries of type 'script' that may contain malicious commands.
    Affected if Any ScriptVars entries of type 'script' exist in the system

A user is affected if bestinformed Web is running with ScriptVars of type 'script' enabled and non-admin users have been granted permissions to create such ScriptVars.

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

Restrict or disable the ability to create ScriptVars with type 'script' to only trusted administrators, review the granular permission assignments, and if possible implement input sanitization to prevent command execution.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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