CVE-2013-7095
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 · uneditedThe XML parser (crm_flex_data) in SAP Customer Relationship Management (CRM) 7.02 EHP 2 has unknown impact and attack vectors related to an XML External Entity (XXE) issue.
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 confidenceXML External Entity (XXE) vulnerability in the crm_flex_data XML parser of SAP Customer Relationship Management 7.02 EHP 2 allows attackers to inject malicious XML containing external entity references, potentially leading to disclosure of internal files, denial of service, or server-side request forgery.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.02CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Confirm SAP CRM versionUse SAP transaction code SM51 to display the SAP system version, or check the SAP System Properties (system info) to identify the CRM release version. Look specifically for version 7.02.Affected if The installed SAP CRM version is exactly 7.02 (note the = in the affected version range indicates this specific version)
-
Locate crm_flex_data componentCheck the SAP CRM system for the presence and status of the crm_flex_data component. This may be listed in SAP transaction code SE11 (Data Dictionary) for data elements, or via transaction code SPAM for installed components related to flex data handling.Affected if The crm_flex_data XML parser component is installed and active in the SAP CRM 7.02 environment
-
Identify XML parser configurationExamine the XML parser or flex data configuration in SAP CRM related to crm_flex_data. This is typically found in customising settings (transaction code SPRO) under Customer Relationship Management -> Flexible Data or XML Processing configurations.Affected if The XML parser configuration for crm_flex_data is present and allows processing of external entity definitions (DOCTYPE declarations)
-
Check for XXE-enabled XML processingReview the XML parser settings or customising for crm_flex_data to determine whether external entity processing is enabled. Look for configuration flags related to DTD processing, external entity resolution, or XXE handling.Affected if The XML parser is configured to process external entities (DTD processing enabled) when handling XML data through crm_flex_data
A system is affected if it runs SAP CRM version 7.02 AND has the crm_flex_data XML parser component active with external entity processing enabled in its configuration.
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 dataDisable XML external entity processing in the crm_flex_data parser configuration or implement input validation to reject XML containing DOCTYPE declarations with external entity definitions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7095 — 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-2013-7095 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