CVE-2025-47410: Apache Geode geode-web Package Vulnerable to CSRF Attacks via Management and Monitoring REST API

org.apache.geode:geode-web Updated 20 Oct 2025

Summary

18/10/2025
Yes i
High
8.8

CVE-2025-47410: Apache Geode is vulnerable to CSRF attacks through GET requests to the Management and Monitoring REST API that could allow an attacker who has tricked a user into giving up their Geode session credentials to submit malic... Affects org.apache.geode:geode-web versions >= 1.10.0, < 1.15.2. Fixed in 1.15.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Apache Geode is an open-source data management platform that provides a distributed in-memory data grid. It is designed to enable high-performance applications by allowing users to store and manage data in a scalable and fault-tolerant manner. The geode-web package specifically offers a web-based interface for managing and monitoring Geode clusters. However, it is susceptible to Cross-Site Request Forgery (CSRF) attacks, which can compromise user sessions and lead to unauthorized command execution.

Vulnerability Detail

The vulnerability arises from the Management and Monitoring REST API of Apache Geode, which allows GET requests without adequate CSRF protection. An attacker can exploit this by tricking a user into making a GET request that executes malicious commands on the target system, leveraging the user's authenticated session. This could lead to unauthorized access and manipulation of data, posing significant security risks to the affected system.

How To Fix

Minimum fixed version

1.15.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users can implement additional CSRF protection mechanisms in their applications, such as validating CSRF tokens for sensitive operations. However, upgrading to the patched version is the recommended approach for long-term security.

Conclusion

In summary, CVE-2025-47410 is a significant vulnerability in the Apache Geode geode-web package that exposes users to CSRF attacks. It is crucial for users to upgrade to version 1.15.2 to mitigate this risk and ensure the security of their applications.

See every vulnerability recorded for org.apache.geode:geode-web →

Share this vulnerability

FAQ

CVE-2025-47410 is a vulnerability in the Apache Geode geode-web package that allows CSRF attacks through GET requests to its Management and Monitoring REST API.

The vulnerability affects Apache Geode versions 1.10.0 through 1.15.1.

You can use Vulert, which monitors open-source vulnerabilities in real-time using just the pom.xml file. Visit Vulert Scanner to check if your application is affected without any signup.

The CVSS score of this vulnerability is 8.8, indicating a high severity level.

If immediate upgrading is not possible, consider implementing additional CSRF protection measures as a temporary workaround.

How To Fix

Minimum fixed version

1.15.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback