dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-0423

MEDIUM · 5.3 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 →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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
In the "bestinformed Web" application, some user input was not properly sanitized. This leads to multiple unauthenticated stored cross-site scripting vulnerabilities. An unauthenticated attacker is able to compromise the sessions of users on the server by injecting JavaScript code into their session using an "Unauthenticated Stored Cross-Site Scripting". The attacker is then able to ride the session of those users and can abuse their privileges on the "bestinformed Web" application.

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

The 'bestinformed Web' application suffers from multiple unauthenticated stored XSS vulnerabilities where user-supplied input is not properly sanitized before storage and display. An attacker can inject malicious JavaScript code that executes in the browsers of other users, enabling session hijacking and privilege escalation.

MitigationImplement robust input validation and output encoding (context-aware escaping) for all user-supplied data, and consider deploying a Content Security Policy (CSP) header to mitigate XSS 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
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/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. Confirm 'bestinformed Web' application presence
    Search for the application in web server directories, check running web services, or review installed packages. Look for directories or services named 'bestinformed' or associated with the product.
    Affected if The application is present in the environment
  2. Identify the application entry points
    Locate the application's web accessible paths (URLs). Check web server configuration files (Apache/nginx/IIS configs) for 'bestinformed' virtual hosts or aliases.
    Affected if The application is web-accessible via HTTP/HTTPS
  3. Locate user input fields
    Review the application's pages for forms or input mechanisms that accept user data such as login fields, registration forms, contact forms, comment fields, search inputs, or profile update fields.
    Affected if User-supplied input fields exist in the application
  4. Test for stored XSS vulnerability
    Using a browser or HTTP client, submit a benign XSS payload such as <script>alert('XSS')</script> or <img src=x onerror=alert('XSS')> into visible input fields. Then navigate away and return to the page or view the stored data to check if the payload executes or is rendered unsanitized.
    Affected if The injected payload is stored and executed/displayed unescaped when the page is revisited
  5. Verify exploitability without authentication
    Attempt the XSS injection described above without logging in or authenticating to the application.
    Affected if The stored XSS is triggered in the browser of another user without requiring authentication

If the 'bestinformed Web' application is present and user input fields store and reflect unsanitized data back to users, the environment is affected by this stored XSS vulnerability.

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

Implement robust input validation and output encoding (context-aware escaping) for all user-supplied data, and consider deploying a Content Security Policy (CSP) header to mitigate XSS execution.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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