dbcve.org
Calendar01Application · Calendar01 Project

CVE-2020-5616

CRITICAL · 9.8 CVSS v3.1 Published 2020-08-04
Fix available
A fix is available. Upgrade to after 1.0.3 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
[Calendar01], [Calendar02], [PKOBO-News01], [PKOBO-vote01], [Telop01], [Gallery01], [CalendarForm01], and [Link01] [Calendar01] free edition ver1.0.0, [Calendar02] free edition ver1.0.0, [PKOBO-News01] free edition ver1.0.3 and earlier, [PKOBO-vote01] free edition ver1.0.1 and earlier, [Telop01] free edition ver1.0.0, [Gallery01] free edition ver1.0.3 and earlier, [CalendarForm01] free edition ver1.0.3 and earlier, and [Link01] free edition ver1.0.0 allows remote attackers to bypass authentication and log in to the product with administrative privileges 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

Multiple PKOBO free edition products (Calendar01, Calendar02, PKOBO-News01, PKOBO-vote01, Telop01, Gallery01, CalendarForm01, and Link01) contain an authentication bypass vulnerability allowing remote attackers to gain administrative access without valid credentials. The specific attack vector is not disclosed in the advisory.

MitigationSince no patch appears to be available for these free edition products, consider migrating to supported versions or alternative solutions with active security maintenance. If continued use is required, implement network-level access controls (e.g., IP whitelisting, VPN) to limit exposure to untrusted networks.

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
Calendar01Application
Affected:= 1.0.0
Calendar02Application
Affected:= 1.0.0
Calendarform01Application
Affected:<= 1.0.3
Gallery01Application
Affected:<= 1.0.3
Link01Application
Affected:= 1.0.0
Pkobo News01Application
Affected:<= 1.0.3
Pkobo Vote01Application
Affected:<= 1.0.1
Telop01Application
Affected:= 1.0.0

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. Identify installed PKOBO products
    Inspect your web server for directories or applications corresponding to the affected product names: Calendar01, Calendar02, Calendarform01, Gallery01, Link01, Pkobo News01, Pkobo Vote01, or Telop01. Check application listings, file systems, or web server configuration for these components.
    Affected if Any of these eight PKOBO products are present on the server
  2. Determine product version
    Locate the version information for the installed PKOBO product. This is typically found in a configuration file, README, about page, or metadata file within the product directory. Compare the discovered version against the affected ranges: Calendar01 (=1.0.0), Calendar02 (=1.0.0), Calendarform01 (<=1.0.3), Gallery01 (<=1.0.3), Link01 (=1.0.0), Pkobo News01 (<=1.0.3), Pkobo Vote01 (<=1.0.1), Telop01 (=1.0.0).
    Affected if The installed version matches or falls within the specified version ranges for any affected product
  3. Verify admin interface exposure
    Determine if the administrative interface or login page for the PKOBO product is accessible from the network. Common paths may include /admin, /login, or product-specific admin directories. Test whether these endpoints respond to HTTP requests.
    Affected if The admin interface is reachable over the network without requiring authentication
  4. Check for authentication enforcement
    Attempt to access restricted admin functions or pages within the PKOBO application. Observe whether the application properly enforces authentication or allows access to administrative features without credentials.
    Affected if Administrative functions are accessible without valid credentials or authentication can be bypassed

You are affected if any PKOBO product (Calendar01, Calendar02, Calendarform01, Gallery01, Link01, Pkobo News01, Pkobo Vote01, or Telop01) matching the specified versions is installed and its admin interface is network-accessible.

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.0.3
Interim mitigation

Since no patch appears to be available for these free edition products, consider migrating to supported versions or alternative solutions with active security maintenance. If continued use is required, implement network-level access controls (e.g., IP whitelisting, VPN) to limit exposure to untrusted networks.

Fix this in Calendar01 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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