dbcve.org
GlpiApplication · Glpi Project

CVE-2025-52567

MEDIUM · 5.0 CVSS v3.1 Published 2025-07-30
Fix available
A fix is available. Upgrade to 10.0.19 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
GLPI is a Free Asset and IT Management Software package, Data center management, ITIL Service Desk, licenses tracking and software auditing. In versions 0.84 through 10.0.18, usage of RSS feeds or external calendars when planning is subject to SSRF exploit. The previous security patches provided since GLPI 10.0.4 were not robust enough for certain specific cases. This is fixed in version 10.0.19.

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 confidence

GLPI versions 0.84 through 10.0.18 contain a Server-Side Request Forgery (SSRF) vulnerability in the planning feature when processing RSS feeds or external calendars. The vulnerability stems from insufficient validation of URLs used to fetch external content, allowing attackers to make the server request arbitrary internal or external resources. Previous security patches since version 10.0.4 were incomplete for certain edge cases.

MitigationUpgrade to GLPI version 10.0.19 or later to obtain the complete fix. As an interim measure, disable RSS feeds and external calendar integrations in the planning module until the upgrade can be performed.

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
GlpiApplication
Affected:>= 0.84, < 10.0.19

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

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

Work through these to decide whether this CVE applies to you.

  1. Check installed GLPI version
    Locate the version.php file in the GLPI root directory and read the $CFG_GLPI['version'] variable, or access the Setup > General > System Information page in the web interface
    Affected if Version is 0.84 through 10.0.18 inclusive
  2. Verify planning module is enabled
    Log in as administrator, navigate to Setup > Plugins or check the main menu for the Planning option. Alternatively, query the database table glpi_plugins for planning-related entries or check glpi_profiles for planning permissions
    Affected if Planning module appears in the menu or database shows it as active
  3. Check for configured RSS feeds
    Navigate to Tools > RSS feeds in the web interface, or query the database: SELECT * FROM glpi_rssfeeds WHERE 1=1
    Affected if Any RSS feeds are configured and active
  4. Check for external calendar integrations
    Navigate to Setup > External links or check user preferences for calendar synchronization settings. Query the database: SELECT * FROM glpi_externallinks WHERE link_type LIKE '%calendar%' or check for ical/caldav configurations in glpi_calendars or related tables
    Affected if External calendar URLs are configured or calendar synchronization is enabled

You are affected if your GLPI version is between 0.84 and 10.0.18 AND the planning module is active with RSS feeds or external calendar integrations configured

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 10.0.19 or later
Fixed in 10.0.19
Interim mitigation

Upgrade to GLPI version 10.0.19 or later to obtain the complete fix. As an interim measure, disable RSS feeds and external calendar integrations in the planning module until the upgrade can be performed.

Recommended fix High confidence

10.0.19

  1. Backup the GLPI database and all files before proceeding with the upgrade
  2. Download GLPI version 10.0.19 from the official GitHub releases page (github.com/glpi-project/glpi/releases) or from the official glpi-project.org website
  3. Extract the new version files to replace the current GLPI installation
  4. Run the upgrade by navigating to the GLPI URL in a web browser and following the on-screen upgrade wizard
  5. Verify that RSS feeds and external calendar planning features function correctly after the upgrade
  6. Confirm the SSRF vulnerability is mitigated by testing that external calendar/RSS inputs no longer trigger requests to internal network resources
Caveat Check the GLPI 10.0.19 release notes for any breaking changes or deprecations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52567 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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