dbcve.org
XoonipsApplication · Riken

CVE-2020-5624

CRITICAL · 9.8 CVSS v3.1 Published 2020-08-28
Fix available
A fix is available. Upgrade to after 3.48 or later.
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
SQL injection vulnerability in the XooNIps 3.48 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

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 XooNIps 3.48 and earlier allows remote unauthenticated attackers to execute arbitrary SQL commands via unspecified input vectors. The lack of proper input validation or parameterized queries in the application enables attackers to inject malicious SQL statements, potentially leading to data exfiltration, modification, or complete database compromise.

MitigationUpgrade to a patched version of XooNIps when available. As an interim control, deploy a web application firewall (WAF) to filter malicious SQL injection payloads, and restrict network access to the application until the patch is applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XoonipsApplication
Affected:<= 3.48

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 XooNIps is installed
    Check your web server's document root for the XooNIps application directory (typically named 'xoonips' or similar). Look for the index.php file and the characteristic XooNIps directory structure.
    Affected if The application is present in your environment
  2. Identify the installed XooNIps version
    Open the version.php or about.html file in the XooNIps installation directory, or check the administration panel's system information page for the version number.
    Affected if The version number is 3.48 or lower
  3. Verify the application is network-accessible
    Confirm the XooNIps web interface is accessible over HTTP/HTTPS from the network. Check your web server configuration for active virtual hosts or aliases pointing to the XooNIps installation.
    Affected if The application is exposed to network traffic without additional access controls

Your environment is affected if XooNIps version 3.48 or earlier is installed and accessible over the network, since this version contains the SQL injection vulnerability that allows unauthenticated remote attackers to execute arbitrary SQL commands.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.48
Interim mitigation

Upgrade to a patched version of XooNIps when available. As an interim control, deploy a web application firewall (WAF) to filter malicious SQL injection payloads, and restrict network access to the application until the patch is applied.

Recommended fix Moderate confidence

Xoonips version 3.49 or later (check xoonips.osdn.jp for exact stable release)

  1. 1. Backup the current Xoonips installation and database before making any changes.
  2. 2. Check the official Xoonips project page (xoonips.osdn.jp) for the latest stable release version.
  3. 3. Download the fixed release (version 3.49 or later if available).
  4. 4. Replace the existing Xoonips files with the new version, preserving custom configurations if required.
  5. 5. Update the database schema if the upgrade includes migration scripts.
  6. 6. Verify the application functions correctly after the upgrade.
  7. 7. Test that the SQL injection vulnerability is no longer present by reviewing the fixed code paths.
Caveat Review release notes for any backward-incompatible changes between 3.48 and the target version; custom modules or templates may require updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xoonips Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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