LiveActive security incident?Get immediate response
CVE Record

CVE-2023-39611: An issue in Software FX Chart FX 7 version 7.0.4962.20829 allows attackers to enumerate and read files from...

An issue in Software FX Chart FX 7 version 7.0.4962.20829 allows attackers to enumerate and read files from the local filesystem by sending crafted web requests.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-39611 is a directory traversal flaw in Software FX Chart FX 7 version 7.0.4962.20829. If the affected web-facing component is reachable, an unauthenticated attacker may read files from the server filesystem. The main business risk is exposure of secrets, configuration files, or sensitive customer and operational data.

Executive priority

Treat as high priority for externally reachable systems because compromise can expose sensitive files without credentials. Internal-only deployments still deserve review, especially where servers store secrets, keys, database credentials, or regulated data. Remediation should start with exposure reduction while vendor fix status is confirmed.

Technical view

The CVE describes CWE-22 path traversal reachable over the network with low complexity, no authentication, and no user interaction. CVSS 3.1 is 7.5, driven by high confidentiality impact only. Public affected metadata is incomplete, but the description identifies Software FX Chart FX 7 version 7.0.4962.20829.

Likely exposure

Exposure is most likely where applications embed or host Software FX Chart FX 7 version 7.0.4962.20829 and expose its web request handling to users or the internet. The CVE bundle does not provide CPEs or broader affected-version ranges, so inventory confirmation is required.

Exploitation context

The source bundle says exploitation uses crafted web requests to enumerate and read local files. There is no CISA KEV listing and no cited source in the bundle confirming active exploitation. Public evidence is sufficient for vulnerability existence, but incomplete for patch status and exploitation prevalence.

Researcher notes

The CVE record is concise and affected-product metadata is sparse. Base scoring indicates confidentiality-only impact, so validation should focus on unauthorized file read exposure and reachable attack surface. Avoid assuming affected versions beyond 7.0.4962.20829 unless vendor or application evidence supports it.

Mitigation direction

  • Identify and prioritize internet-facing Chart FX 7 deployments.
  • Restrict external access to affected Chart FX endpoints.
  • Remove or disable the component where it is not required.
  • Check Software FX or application vendor guidance for fixed versions.
  • Monitor server logs for suspicious file traversal attempts.

Validation and detection

  • Confirm whether Chart FX 7 version 7.0.4962.20829 is deployed.
  • Map which applications expose Chart FX functionality over HTTP.
  • Review application and web server logs for unusual file-read patterns.
  • Verify least-privilege filesystem access for the application process.
  • Document whether vendor patch or compensating control is in place.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-39611 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-39611Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.