dbcve.org
DoyocmsApplication · Doyocms Project

CVE-2020-19803

HIGH · 8.8 CVSS v3.1 Published 2023-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
Cross Site Request Forgery vulnerability found in Milken DoyoCMS v.2.3 allows a remote attacker to execute arbitrary code via the background system settings.

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

Cross Site Request Forgery (CSRF) vulnerability in Milken DoyoCMS v2.3 allows remote attackers to trick authenticated administrators into submitting malicious requests to the background system settings interface, potentially leading to arbitrary code execution on the server.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations in the admin panel, particularly system settings; enforce SameSite cookie attributes; validate Origin/Referer headers.

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
DoyocmsApplication
Affected:= 2.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Doyocms installation and version
    Inspect the application footer, about page, or source code for version number '2.3' or check for files like version.php, about.html, or common Doyocms version disclosure paths
    Affected if The installed version is exactly 2.3 (Doyocms Project Doyocms)
  2. Confirm admin panel access
    Navigate to the background/admin login page and verify the Doyocms admin interface is accessible (common paths: /admin, /admin.php, /index.php?m=admin, or /backend)
    Affected if The admin panel is reachable and uses Doyocms 2.3
  3. Check if administrator session is active
    Log in to the admin panel and verify an authenticated session is established; check for admin session cookies
    Affected if An authenticated administrator session exists in the browser
  4. Inspect system settings page for anti-CSRF tokens
    Access the system settings interface (typically under Settings, System Config, or similar admin menu), view the HTML source, and look for CSRF tokens in forms (hidden input fields with names like 'token', 'csrf_token', 'security_code', or '__hash__')
    Affected if Forms on the system settings page lack anti-CSRF token fields or use predictable/static tokens
  5. Verify Referer/Origin header validation
    Use a browser proxy or curl to submit a request to system settings without a valid Referer or Origin header; check if the request is processed without rejection
    Affected if The application accepts state-changing requests without validating Referer or Origin headers
  6. Test for CSRF vulnerability
    Craft a malicious HTML page that auto-submits a form to the system settings endpoint (e.g., modifying configuration) and attempt to trigger it from an authenticated admin browser context; observe if the action executes
    Affected if The system settings can be modified via cross-origin requests without anti-CSRF protection

You are affected if running Doyocms version 2.3 AND the admin panel system settings forms lack anti-CSRF token protection, allowing attackers to trigger unauthorized configuration changes via authenticated administrator sessions.

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 anti-CSRF tokens (synchronizer token pattern) on all state-changing operations in the admin panel, particularly system settings; enforce SameSite cookie attributes; validate Origin/Referer headers.

Fix this in Doyocms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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