Skip to content

CVE-2026-8347

Is CVE-2026-8347 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
PoC (unverified)
Metasploit/EDB/PoC
Base severity
4.3 Medium
CVSS
Exploitation prob.
0.2%
FIRST EPSS
Weakness
CWE-639
CWE

Moderate signals. Triage by your actual exposure and reachability.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
None
in the wild
Automatable
No
at scale
Technical impact
Partial
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Track
  • high impact → Track

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

public exploits

links to sources — we don’t host code

Unverified proof-of-concept code has been published. It may or may not be functional — assess before relying on it.

affected packages

GHSA-jqvq-gv67-3567 · GitHub rates it low
  • Composerconcrete5/concrete5
    Vulnerable
    < 9.5.1
    Fixed in
    9.5.1

Source: GitHub Advisory Database (CC-BY 4.0), via OSV.dev. Check your lockfile version against the ranges above.

baseline read

auto · not a community verdict

Low signal — verdict needed

Few public signals point to active risk. Whether a scanner hit here is a true or false positive depends on your version and config — community verdicts decide.

Based on CVSS · FIRST EPSS

Confirm or dispute →
Affected:Concretecms

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Concrete CMS 9.5.0 and below is vulnerable to IDOR + wrong-authorization-level in the Express association Reorder dialog.  This can cause Cross-entity state tampering with view-only permission on one entry. To be affected, a website has to be using express and relying on express entity ordering. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 2.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.

Published

Embed this verdict
TruePositive verdict for CVE-2026-8347
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-8347/badge.svg)](https://www.truepositive.app/cve/CVE-2026-8347)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-8347"><img src="https://www.truepositive.app/cve/CVE-2026-8347/badge.svg" alt="TruePositive verdict for CVE-2026-8347"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. CISA SSVC assessment · exploitation: none
  2. Published by NVD

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    No confirmed in-the-wild exploitation or public exploit was found for this yet.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-639.