Commons BeanutilsApplication · Apache
CVE-2025-48734
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 · uneditedImproper Access Control vulnerability in Apache Commons. A special BeanIntrospector class was added in version 1.9.2. This can be used to stop attackers from using the declared class property of Java enum objects to get access to the classloader. However this protection was not enabled by default. PropertyUtilsBean (and consequently BeanUtilsBean) now disallows declared class level property access by default. Releases 1.11.0 and 2.0.0-M2 address a potential security issue when accessing enum properties in an uncontrolled way. If an application using Commons BeanUtils passes property paths from an external source directly to the getProperty() method of PropertyUtilsBean, an attacker can access the enum’s class loader via the “declaredClass” property available on all Java “enum” objects. Accessing the enum’s “declaredClass” allows remote attackers to access the ClassLoader and execute arbitrary code. The same issue exists with PropertyUtilsBean.getNestedProperty(). Starting in versions 1.11.0 and 2.0.0-M2 a special BeanIntrospector suppresses the “declaredClass” property. Note that this new BeanIntrospector is enabled by default, but you can disable it to regain the old behavior; see section 2.5 of the user's guide and the unit tests. This issue affects Apache Commons BeanUtils 1.x before 1.11.0, and 2.x before 2.0.0-M2.Users of the artifact commons-beanutils:commons-beanutils 1.x are recommended to upgrade to version 1.11.0, which fixes the issue. Users of the artifact org.apache.commons:commons-beanutils2 2.x are recommended to upgrade to version 2.0.0-M2, which fixes the 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 · high confidenceApache Commons BeanUtils allows access to the 'declaredClass' property on Java enum objects through PropertyUtilsBean.getProperty() and getNestedProperty(). This exposes the enum's ClassLoader, enabling remote attackers to execute arbitrary code. A protective BeanIntrospector existed since 1.9.2 but was not enabled by default. Versions 1.11.0 and 2.0.0-M2 enable this protection by default.
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
Commons BeanutilsApplication
>= 1.0, < 1.11.0= 2.0.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Apache Commons BeanUtils library versionLocate the commons-beanutils.jar or commons-beanutils2.jar in your project's dependencies (Maven pom.xml, Gradle build.gradle, or in the lib/ directory). Check the version attribute against the affected ranges: < 1.11.0 for beanutils 1.x, or = 2.0.0-M2 for beanutils2.Affected if The version is 1.x < 1.11.0 or 2.x = 2.0.0-M2.
-
Find usage of vulnerable PropertyUtils methodsSearch source code for calls to org.apache.commons.beanutils.PropertyUtilsBean.getProperty() or getNestedProperty(), or the static equivalents org.apache.commons.beanutils.PropertyUtils.getProperty() / getNestedProperty(). Review the method signatures in your codebase.Affected if These methods are called with external property path arguments (e.g., user-controlled input).
-
Verify external input reaches vulnerable methodsTrace data flow from request parameters, API inputs, or configuration files to the PropertyUtils getProperty/getNestedProperty calls identified in step 2. Determine if untrusted input flows directly to the property path parameter.Affected if External or untrusted input is passed directly as the property path argument without sanitization.
-
Confirm enum objects are processed through BeanUtilsReview code paths that pass Java enum values to BeanUtils property operations. Check if enums are stored in beans, collections, or maps that get processed via the vulnerable methods.Affected if Enum objects are accessible through the property paths processed by the vulnerable methods.
You are affected if you use a vulnerable BeanUtils version (pre-1.11.0 for 1.x, or 2.0.0-M2 for 2.x) AND external input can reach PropertyUtils.getProperty() or getNestedProperty() with enum objects in the property path chain.
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.
dbcve · scoped1.11.0
Upgrade Apache Commons BeanUtils to version 1.11.0 (for 1.x) or 2.0.0-M2 (for 2.x) to enable the declaredClass property suppression by default. Verify that no application code relies on accessing enum declaredClass properties.
1.11.0 for commons-beanutils:commons-beanutils (1.x); 2.0.0-M2 for org.apache.commons:commons-beanutils2 (2.x)
- Identify the exact artifact and version of Commons BeanUtils used in your project (check pom.xml, build.gradle, or dependency management)
- If using commons-beanutils:commons-beanutils (1.x), upgrade to version 1.11.0
- If using org.apache.commons:commons-beanutils2 (2.x), upgrade to version 2.0.0-M2
- Update the version in your dependency management file (pom.xml, build.gradle, or equivalent)
- Rebuild and test your application to ensure the upgrade does not break functionality
- If your application explicitly relies on accessing the 'declaredClass' property of enum objects and experiences issues, review section 2.5 of the Commons BeanUtils user guide for configuration options to re-enable the old behavior (not recommended for untrusted input)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Commons Beanutils
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48734 — 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-48734 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