LiveActive security incident?Get immediate response
CVE Record

CVE-2025-52164: Software GmbH Agorum core open v11.9.2 & v11.10.1 was discovered to store credentials in plaintext.

Software GmbH Agorum core open v11.9.2 & v11.10.1 was discovered to store credentials in plaintext.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Agorum core open versions 11.9.2 and 11.10.1 were reported to store credentials in plaintext. If an attacker can access the relevant storage, backups, or application data, credentials may be exposed and reused. The public bundle rates this high with CVSS 8.2, but does not provide product lifecycle or patch details.

Executive priority

Treat this as a high-priority exposure review if Agorum core open is in use. The main business risk is credential disclosure leading to follow-on access, not immediate service outage. Prioritize version inventory, vendor guidance, access restriction, and credential rotation.

Technical view

The issue is classified as CWE-256, plaintext storage of credentials, with CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N. The CVE text names Agorum core open v11.9.2 and v11.10.1, while structured affected-product data is incomplete. No exploit mechanism, affected storage location, or fix version is included in the supplied bundle.

Likely exposure

Organizations running Agorum core open 11.9.2 or 11.10.1 should assume possible credential exposure until vendor guidance proves otherwise. Exposure depends on who can access the affected application data, configuration, filesystem, database, or backups.

Exploitation context

The bundle does not cite active exploitation, and the CVE is not marked as CISA KEV. The CVSS vector indicates network-reachable, low-complexity, unauthenticated conditions, but no public exploit steps or proof-of-concept details are provided here.

Researcher notes

Evidence is thin in the supplied bundle. The CVE names two versions and CWE-256, but the structured affected fields are n/a and no fix, storage path, or exploit evidence is provided. Validate against the referenced advisory before broad claims.

Mitigation direction

  • Check the usd HeroLab advisory and vendor guidance for fixed versions or official workarounds.
  • Inventory Agorum core open deployments and identify versions 11.9.2 and 11.10.1.
  • Restrict administrative and backend access while assessing exposure.
  • Rotate credentials that may have been stored by affected instances.
  • Review backups and exports for retained plaintext credentials.

Validation and detection

  • Confirm whether any deployed instance runs Agorum core open 11.9.2 or 11.10.1.
  • Review vendor advisory details for exact affected components and remediation status.
  • Identify where application credentials are stored and whether they are plaintext.
  • Check access controls around application storage, backups, and administrative interfaces.
  • Document credential rotation status for accounts used by affected deployments.
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 · low confidence lookup

CWE-256: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2025-52164 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
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

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
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2025-52164Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
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-256 · source CWE mapping

Plaintext Storage of a Password

Plaintext Storage of a Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.