dbcve.org
MatchasnsApplication · Icz

CVE-2015-5644

MEDIUM · 6.8 CVSS v2.0 Published 2015-10-06
Fix available
A fix is available. Upgrade to after 1.3.6 or later.
See remediation →
77/100
Remediation priority · High
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
The installer in ICZ MATCHA SNS before 1.3.7 does not properly configure the database, which allows remote attackers to execute arbitrary PHP code 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

The ICZ MATCHA SNS installer before version 1.3.7 fails to properly secure the database configuration during initial setup. This misconfiguration allows remote attackers to execute arbitrary PHP code on the server, likely through database manipulation or exploiting the improperly configured installer pathways.

MitigationUpgrade to ICZ MATCHA SNS version 1.3.7 or later, which contains the proper database configuration fix. If already deployed, audit the database configuration and web server permissions immediately.

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
MatchasnsApplication
Affected:<= 1.3.6

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 ICZ MATCHA SNS is installed
    Search your web server directories for the presence of ICZ MATCHA SNS application files, typically found in directories named 'matchasns', 'matcha', or similar. Check for files containing 'matchasns' or 'MATCHA' in the application structure.
    Affected if The application is present on the server and is ICZ MATCHA SNS version 1.3.6 or earlier.
  2. Determine installed version
    Locate the version information file or header within the ICZ MATCHA SNS installation. Common locations include a version.php file, a config file, or the installer script itself. Compare the version number to the affected range of version 1.3.6 and below.
    Affected if The installed version is 1.3.6 or any version lower than 1.3.6.
  3. Check if installer is exposed
    Verify whether the installer pathway is still accessible on the web server. Attempt to access common installer URLs such as '/install/', '/installer/', or '/setup/' appended to the application path. Also check for remaining installer scripts or setup files in the web root.
    Affected if The installer setup scripts or pathways remain accessible without authentication on the server.
  4. Inspect database configuration security
    Examine the database configuration file (commonly config.php, db.php, or similar in the application root or includes directory) to verify if database credentials are properly secured. Check if the configuration file has appropriate file permissions (should not be world-writable) and if sensitive database credentials are stored securely.
    Affected if Database configuration files are found to be world-readable, improperly secured, or contain default/weak credentials.
  5. Check for unauthorized database modifications
    Review database tables, particularly any tables related to user accounts, settings, or content, for unexpected PHP code or suspicious stored procedures that could indicate attempted or successful exploitation through database manipulation.
    Affected if Unexpected PHP code sequences or suspicious database entries are found in configuration or content tables.

A defender is affected if ICZ MATCHA SNS version 1.3.6 or earlier is installed and the installer remains accessible or database configuration files are improperly secured.

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
Upgrade available Upgrade to a release after 1.3.6
Interim mitigation

Upgrade to ICZ MATCHA SNS version 1.3.7 or later, which contains the proper database configuration fix. If already deployed, audit the database configuration and web server permissions immediately.

Fix this in Matchasns Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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