CVE-2019-10015
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 · uneditedbaigoStudio baigoSSO v3.0.1 allows remote attackers to execute arbitrary PHP code via the first form field of a configuration screen, because this code is written to the BG_SITE_NAME field in the opt_base.inc.php file.
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 confidencebaigoSSO v3.0.1 contains an authenticated remote code execution vulnerability where the BG_SITE_NAME configuration parameter in the admin configuration screen is written directly to opt_base.inc.php without sanitization, allowing attackers to inject arbitrary PHP code that gets executed on the server.
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= 3.0.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 baigoSSO version 3.0.1 is installedLocate the baigoSSO installation directory and check the version. Common locations include a version.php file, a readme file, or the admin panel About page. Compare your installed version to the affected range.Affected if The installed version is exactly 3.0.1
-
Verify admin panel is accessibleCheck if the baigoSSO admin login page is reachable. Common paths include /admin/, /sso/admin/, or check the application's index for admin links.Affected if The admin panel is accessible and authentication is possible (required for authenticated RCE)
-
Locate opt_base.inc.php configuration fileSearch for the file opt_base.inc.php within the baigoSSO installation directory, typically found in a config, include, or similar directory.Affected if The file opt_base.inc.php exists in the application directory
-
Inspect BG_SITE_NAME parameter for injected codeOpen opt_base.inc.php and locate the BG_SITE_NAME configuration parameter. Examine its value to see if it contains raw PHP code such as system(), exec(), passthru(), shell_exec(), or eval().Affected if The BG_SITE_NAME parameter contains executable PHP code or suspicious function calls rather than plain text
-
Check for unexpected PHP code in configuration filesReview all PHP configuration files generated by baigoSSO (not just opt_base.inc.php) for any parameters that contain opening PHP tags followed by code execution functions.Affected if Any configuration parameter contains injectable PHP code
You are affected if you are running baigoSSO version 3.0.1 with an accessible admin panel AND the opt_base.inc.php file contains PHP code in the BG_SITE_NAME parameter.
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 strict input validation and output escaping on all configuration parameters before writing to PHP files; consider storing configuration in a non-executable format (JSON/INI) rather than direct PHP code generation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10015 — 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-10015 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