CVE-2019-15089
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 · uneditedAn issue was discovered in PRiSE adAS 1.7.0. Forms have no CSRF protection, letting an attacker execute actions as the administrator.
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 confidencePRiSE adAS 1.7.0 contains forms that lack CSRF (Cross-Site Request Forgery) protection mechanisms. An attacker can craft malicious links or pages that, when triggered by an authenticated administrator session, cause the browser to unknowingly submit authorized requests to the application, allowing the attacker to execute administrative actions.
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= 1.7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm PRiSE adAS versionAccess the application login page or administrative interface and identify the installed version. This is typically displayed in the login page footer, an 'About' page, or can be inferred from the application banner/version endpoint. Compare against the affected version 1.7.0.Affected if The installed version is exactly 1.7.0 of PRiSE adAS
-
Examine login form HTML for CSRF tokensView the page source of the login form (or any state-changing form in the admin area) using browser developer tools or by viewing the HTML source. Search for input fields with names like 'csrf', 'token', 'nonce', '_token', or 'xsrf' that contain unpredictable values.Affected if No anti-CSRF token fields are present in the form HTML
-
Check form submission behaviorSubmit a test form (e.g., login, or any admin action) while monitoring the HTTP request in the browser network tab. Verify whether the request includes a unique, unpredictable token parameter in the request body or headers.Affected if The form submits without requiring a unique CSRF token in the request
-
Verify Origin/Referer header validationSubmit a cross-origin form request (e.g., from a different domain or by manipulating the Origin header) to a state-changing endpoint. Observe whether the server rejects the request due to missing or invalid Origin/Referer headers.Affected if The server accepts requests without validating the Origin or Referer header
You are affected if PRiSE adAS version 1.7.0 is installed and the application forms lack anti-CSRF token validation or Origin/Referer header checks.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens on all state-changing forms and validate the Origin/Referer header on server-side form handlers. ConsiderSameSite cookie attributes to provide additional defense-in-depth.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15089 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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