CVE-2025-52162
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 · uneditedagorum Software GmbH Agorum core open v11.9.2 & v11.10.1 was discovered to contain an XML External Entity (XXE) via the RSSReader endpoint. This vulnerability allows attackers to access sensitive data via providing a crafted XML input.
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 · high confidenceThe Agorum core open application versions 11.9.2 and 11.10.1 contains an XML External Entity (XXE) vulnerability in the RSSReader endpoint. Attackers can exploit this by submitting crafted XML input containing external entity references, allowing them to read sensitive files from the server or perform Server-Side Request Forgery (SSRF) attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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.
-
Identify installed Agorum versionCheck the application version through the admin interface or version file (typically found in installation directories or About pages). Compare against affected versions 11.9.2 and 11.10.1.Affected if Running version 11.9.2 or 11.10.1 of Agorum core open application
-
Determine if RSSReader endpoint is enabledLocate and inspect the RSSReader module or endpoint configuration in the application settings, web.xml, or module configuration files. Check whether the RSSReader feature is actively exposed.Affected if RSSReader endpoint is enabled and accessible in the application
-
Verify XML parser configuration for the RSSReaderInspect the XML parser settings used by the RSSReader component. Look for configuration files or code that handle XML parsing for this endpoint, specifically checking whether external entity processing or DTD processing is enabled.Affected if XML parser allows external entity (DTD/XXE) processing for the RSSReader endpoint
-
Test for XXE vulnerability exposureIf you have access to test environments, send a benign XXE payload to the RSSReader endpoint and observe whether the parser processes external entities. In production, review access logs for the RSSReader endpoint.Affected if The RSSReader endpoint accepts and processes XML input without blocking external entities
A user is affected if running Agorum core versions 11.9.2 or 11.10.1 with the RSSReader endpoint enabled and the XML parser configured to allow external entity processing.
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 external entity processing and DTD processing in the XML parser used by the RSSReader endpoint, and implement strict input validation for all XML submissions.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52162 — 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-2025-52162 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