CVE-2020-35674
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 · uneditedBigProf Online Invoicing System before 2.9 suffers from an unauthenticated SQL Injection found in /membership_passwordReset.php (the endpoint that is responsible for issuing self-service password resets). An unauthenticated attacker is able to send a request containing a crafted payload that can result in sensitive information being extracted from the database, eventually leading into an application takeover. This vulnerability was introduced as a result of the developer trying to roll their own sanitization implementation in order to allow the application to be used in legacy environments.
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 confidenceUnauthenticated SQL injection vulnerability in /membership_passwordReset.php of BigProf Online Invoicing System versions prior to 2.9. The developer implemented custom input sanitization instead of using parameterized queries, allowing attackers to inject malicious SQL payloads via the password reset endpoint and extract sensitive data or achieve application takeover.
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< 2.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm BigProf Online Invoicing System installationIdentify the application by locating characteristic files in the web root such as config.php, or check HTTP response headers and footer content for 'BigProf' or 'Online Invoicing' branding.Affected if The application is not present or this is a different product
-
Verify the installed versionLocate version information in the application, typically found in a version.php file, config.php, or a README file within the application directory. Compare your version to the affected range of versions prior to 2.9.Affected if Version is less than 2.9 or version information cannot be located
-
Check for vulnerable endpoint existenceLocate the file membership_passwordReset.php in the web-accessible directory structure. This file is typically found in the application root or membership folder.Affected if The file membership_passwordReset.php exists in the deployment
-
Confirm custom sanitization is usedIf code access is available, review membership_passwordReset.php and locate the database query logic. The vulnerability exists because custom input sanitization is used instead of parameterized queries.Affected if Custom sanitization functions are present in the password reset code rather than prepared statements
The environment is affected if BigProf Online Invoicing System version is below 2.9 and the membership_passwordReset.php endpoint is present and accessible.
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.
dbcve · scoped2.9
Upgrade to version 2.9 or later. If upgrading is not feasible, replace the custom sanitization logic with proper prepared statements/parameterized queries in the password reset code and validate all database interactions.
2.9
- Obtain version 2.9 of BigProf Online Invoicing System from the official vendor (BigProf Software)
- Backup the existing database and application files before upgrading
- Replace the existing application files with the version 2.9 files
- Run any database migration scripts provided with version 2.9 if applicable
- Verify the membership_passwordReset.php endpoint is properly updated and no longer contains the vulnerable sanitization code
- Test that password reset functionality works correctly after the upgrade
- Confirm the SQL injection vulnerability is remediated by attempting to inject payload strings in the email parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35674 — 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-2020-35674 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