CVE-2026-39052
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 · uneditedOinone Pamirs 7.0.0 contains a code execution vulnerability via ScriptRunner. The method ScriptRunner.run(String expression, String type, Map<String, Object> context) evaluates attacker-controlled script expressions through the underlying script engine without sandboxing or allowlist restrictions.
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 confidenceOinone Pamirs 7.0.0 contains an unsafe script evaluation vulnerability in ScriptRunner.run(). The method accepts attacker-controlled expression, type, and context parameters and passes them directly to the underlying script engine without sandboxing or allowlist restrictions, enabling arbitrary code execution.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 installationSearch for Pamirs JAR files, WAR files, or installation directories on the system. Check application deployment folders, lib directories, or application server directories.Affected if Oinone Pamirs version 7.0.0 is found installed.
-
Verify installed versionLocate version metadata such as manifest files, version.properties, or build descriptors (pom.xml, build.gradle) within the Pamirs installation. Run: find /path/to/pamirs -name 'version*' -o -name 'pom.xml' 2>/dev/nullAffected if The installed version is 7.0.0 or falls within the 7.x branch without security patches.
-
Locate ScriptRunner classSearch the application codebase or deployed JAR/WAR files for the ScriptRunner class. Use: grep -r 'class ScriptRunner' or decompile JAR files to inspect classes.Affected if The ScriptRunner class exists in the Oinone Pamirs installation.
-
Inspect ScriptRunner.run() usageSearch for invocations of the run() method and examine whether it accepts external input. Look for code patterns like: scriptRunner.run(expression, type, context) or similar parameter combinations.Affected if The run() method is called with user-controllable expression, type, or context parameters.
-
Check for input validation on script parametersReview the code flow leading to ScriptRunner.run() calls. Determine if there is any sanitization, validation, or allowlisting applied to the expression, type, and context parameters before they reach the script engine.Affected if No sandboxing, allowlisting, or input validation is found on the parameters passed to ScriptRunner.run().
A user is affected if Oinone Pamirs 7.0.0 is installed and the ScriptRunner.run() method is accessible with unsanitized attacker-controlled input reaching the script engine.
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 script engine sandboxing or an allowlist of permitted expressions to restrict which scripts can be executed. Validate and sanitize all inputs to ScriptRunner.run() before evaluation.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39052 — 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-39052 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