dbcve.org
Simple InvoicesApplication · Simpleinvoices

CVE-2017-8930

HIGH · 8.8 CVSS v3.0 Published 2017-05-14
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
Multiple cross-site request forgery (CSRF) vulnerabilities in Simple Invoices 2013.1.beta.8 allow remote attackers to hijack the authentication of admins for requests that can (1) create new administrator user accounts and take over the entire application, (2) create regular user accounts, or (3) change configuration parameters such as tax rates and the enable/disable status of PayPal payment modules.

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

Multiple CSRF vulnerabilities in Simple Invoices 2013.1.beta.8 allow remote attackers to create administrator or regular user accounts and modify configuration parameters (tax rates, PayPal module status) by tricking authenticated admins into visiting malicious URLs.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing forms and validate tokens on the server side for admin 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
Simple InvoicesApplication
Affected:= 2013.1

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 Simple Invoices installation
    Check if Simple Invoices web application is running by accessing the application's login page or checking for Simple Invoices banners/footers in the HTML response
    Affected if The application is not Simple Invoices or is a different product entirely
  2. Determine the installed version
    Look for version information in the application (typically in the footer, About page, or in a config/version file). Common paths include checking the main dashboard, admin panel, or examining HTTP headers from the server
    Affected if The installed version is 2013.1 or 2013.1.beta.8
  3. Check for CSRF tokens in user creation forms
    Log in as an administrator and navigate to the user creation/add form. View the page source (right-click > View Page Source) and search for hidden input fields containing 'token', 'csrf', or 'nonce' related to the user creation form
    Affected if No hidden CSRF token field is present in the user creation form HTML
  4. Check for CSRF tokens in configuration forms
    Navigate to the configuration settings page (tax rates, PayPal module settings). View the page source and check if state-changing configuration forms contain hidden CSRF token fields
    Affected if No CSRF token field exists in configuration/modification forms
  5. Verify server-side CSRF validation
    If code access is available, check the backend scripts that handle user creation and configuration updates for server-side validation of CSRF tokens. Look for code that validates 'token', 'csrf', or 'nonce' parameters before processing requests
    Affected if The server-side code does not validate CSRF tokens for admin actions

If Simple Invoices version 2013.1 is running and the user/account creation or configuration forms lack anti-CSRF token fields, the environment is affected by this vulnerability.

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 forms and validate tokens on the server side for admin actions.

Fix this in Simple Invoices Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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