LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25912: A XML External Entity (XXE) vulnerability was discovered in symphony\lib\toolkit\class.xmlelement.php in Sy...

A XML External Entity (XXE) vulnerability was discovered in symphony\lib\toolkit\class.xmlelement.php in Symphony 2.7.10 which can lead to an information disclosure or denial of service (DOS).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-25912 is an XML External Entity issue reported in Symphony 2.7.10. In practical terms, unsafe XML handling could expose information or cause denial of service. The public bundle does not provide severity scoring, affected CPEs, exploit evidence, or a confirmed fixed release.

Executive priority

Treat this as a targeted validation item, not an emergency based on current evidence. Prioritize if Symphony 2.7.10 is internet-facing or processes untrusted XML. Business urgency depends on confirmed exposure because severity and patch details are not provided.

Technical view

The vulnerability is described in symphony\lib\toolkit\class.xmlelement.php in Symphony 2.7.10. It is an XXE flaw with potential information disclosure or denial-of-service impact. The available sources do not define CVSS, CWE, authentication requirements, reachable features, patch version, or exploit maturity.

Likely exposure

Likely exposure is limited to organizations running Symphony CMS 2.7.10, especially where XML-processing functionality is reachable by users or integrations. The source bundle does not confirm broader version impact, product CPEs, or whether authentication is required.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Public evidence is limited to the CVE description and the linked GitHub issue, so exploitability details remain incomplete.

Researcher notes

Evidence is sparse: no CVSS, CPE, CWE, fixed version, or exploit details are included. Analysis should focus on confirming Symphony 2.7.10 usage, reachability of XML parsing, and vendor issue context without assuming impacts beyond information disclosure or denial of service.

Mitigation direction

  • Inventory Symphony CMS deployments and identify any running version 2.7.10.
  • Review the linked SymphonyCMS issue and vendor guidance for fixed versions or official workarounds.
  • Prioritize externally reachable or integration-facing deployments for assessment.
  • Apply vendor-confirmed updates or configuration guidance when available.
  • Use compensating access controls for exposed XML-processing paths pending vendor confirmation.

Validation and detection

  • Confirm application version and code path presence for class.xmlelement.php.
  • Map routes, plugins, or integrations that can submit XML-like content.
  • Check vendor issue history for patch references or affected-version clarification.
  • Review logs for unusual XML-processing errors or denial-of-service symptoms.
  • Document whether affected functionality is reachable anonymously, authenticated, or internal only.
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.

cve · low confidence lookup

CVE-2020-25912 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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