CVE-2026-8734
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 · uneditedA vulnerability was determined in Oinone Pamirs up to 7.2.0. Affected by this issue is the function RSQLToSQLNodeConnector.makeVariable of the component queryListByWrapper Interface. This manipulation causes sql injection. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceSQL injection vulnerability in Oinone Pamirs up to 7.2.0 within the RSQLToSQLNodeConnector.makeVariable function of the queryListByWrapper interface. Remote attackers can exploit unsanitized user input being directly incorporated into SQL queries, potentially allowing unauthorized data access or manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify Oinone Pamirs installationLocate the Oinone Pamirs application in your environment - check for its installation directory, deployed artifacts, or running services that correspond to this product.Affected if Oinone Pamirs is present in the environment
-
Determine installed versionCheck the version of Oinone Pamirs by inspecting the application metadata, build files, or runtime version information. Compare your version to the affected range (up to and including 7.2.0).Affected if Installed version is 7.2.0 or earlier
-
Verify RSQLToSQLNodeConnector component is in useInspect the application codebase or deployed modules for the presence of the RSQLToSQLNodeConnector class, specifically the makeVariable method.Affected if The RSQLToSQLNodeConnector.makeVariable method is present and accessible
-
Confirm queryListByWrapper interface exposureCheck if the queryListByWrapper interface or endpoint is exposed and accessible within the application, as this is the attack vector for the vulnerability.Affected if queryListByWrapper interface is exposed and accessible to users or external systems
-
Inspect user input handling in makeVariableReview the source code or decompile the application to examine how user input is processed in the makeVariable function - look for direct SQL string concatenation without parameterization.Affected if User input is directly concatenated into SQL queries without sanitization or parameterized binding
You are affected if Oinone Pamirs version 7.2.0 or earlier is installed and the queryListByWrapper interface with RSQLToSQLNodeConnector.makeVariable is accessible without proper input sanitization.
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 dataUpgrade to a patched version if available; otherwise, implement parameterized queries or proper input validation/sanitization in the makeVariable function to neutralize SQL injection vectors.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8734 — 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-2026-8734 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