dbcve.org
FlarumApplication

CVE-2019-13183

HIGH · 8.8 CVSS v3.0 Published 2019-07-07
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
Flarum before 0.1.0-beta.9 allows CSRF against all POST endpoints, as demonstrated by changing admin 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 · high confidence

Flarum before version 0.1.0-beta.9 lacks proper Cross-Site Request Forgery (CSRF) protection on POST endpoints. The application fails to validate anti-CSRF tokens, allowing attackers to craft malicious requests that trick authenticated users into performing unintended administrative actions such as modifying admin settings.

MitigationUpgrade to Flarum 0.1.0-beta.9 or later which implements proper CSRF token validation on all POST endpoints.

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
FlarumApplication
Affected:= 0.1.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 installed Flarum version
    Check the composer.json file in the Flarum root directory for the 'flarum/core' version entry, or look for a version file in the vendor directory
    Affected if The installed version is 0.1.0 or any version earlier than 0.1.0-beta.9
  2. Locate POST endpoint handling code
    Inspect the Flarum installation's vendor/flarum/core/src directory, specifically looking for Controller classes that handle POST requests in the admin area
    Affected if The controllers do not contain code to validate an anti-CSRF token on POST requests
  3. Verify CSRF token validation absence
    Search the codebase for 'csrf' or 'token' validation logic within POST request handlers in the admin controllers
    Affected if No anti-CSRF token validation routine is found in the admin POST endpoint handlers
  4. Check admin session configuration
    Examine the session configuration file or the application's bootstrap files for any CSRF token handling setup
    Affected if No CSRF token generation, storage, or validation mechanism is configured for admin sessions

A user is affected if their Flarum installation is version 0.1.0 or earlier (prior to beta.9) and lacks CSRF token validation on admin POST endpoints.

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

Upgrade to Flarum 0.1.0-beta.9 or later which implements proper CSRF token validation on all POST endpoints.

Fix this in Flarum Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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