dbcve.org
SolrApplication · Apache

CVE-2025-24814

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 9.8.0 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable

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
Core creation allows users to replace "trusted" configset files with arbitrary configuration Solr instances that (1) use the "FileSystemConfigSetService" component (the default in "standalone" or "user-managed" mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual "trusted" configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as "trusted" and can use "<lib>" tags to add to Solr's classpath, which an attacker might use to load malicious code as a searchComponent or other plugin. This issue affects all Apache Solr versions up through Solr 9.7.  Users can protect against the vulnerability by enabling authentication and authorization on their Solr clusters or switching to SolrCloud (and away from "FileSystemConfigSetService").  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of "<lib>" tags by default.

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

In vulnerable Solr deployments using FileSystemConfigSetService without authentication, attackers can replace trusted configset files with malicious ones containing <lib> tags that load arbitrary code into Solr's classpath, enabling remote code execution.

MitigationEnable authentication and authorization on Solr clusters, or upgrade to Solr 9.8.0+ which disables <lib> tags by default, or migrate to SolrCloud mode.

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
SolrApplication
Affected:< 9.8.0

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

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 Solr version
    Run `solr -v` or inspect the Solr admin UI version display, or check the version in the solr JAR filename under $SOLR_HOME/server/solr-webapp/
    Affected if version is below 9.8.0
  2. Verify if Solr authentication is enabled
    Check the solr.in.sh or solr.in.cmd file for `SOLR_AUTH_TYPE` and `SOLR_AUTHENTICATION_PLUGIN` settings, or query the /api/cluster/security/authentication endpoint
    Affected if no authentication plugin is configured (SOLR_AUTH_TYPE not set or set to 'none')
  3. Determine if Solr is running in standalone mode (FileSystemConfigSetService)
    Check if the solr.xml configuration file under $SOLR_HOME/server/solr/ defines <solrcloud> mode or inspect the startup logs for 'Solr started in Standalone mode' versus 'Solr started in SolrCloud mode'
    Affected if Solr is running in standalone (non-SolrCloud) mode where FileSystemConfigSetService is used
  4. Check if configset upload/modification is possible
    Inspect the internal.configs permission in security.json or verify write access to the $SOLR_HOME/server/solr/configsets directory where config files are stored
    Affected if configset directory is writable or internal.configs permission allows uploads without authentication

A user is affected if running Solr version below 9.8.0 in standalone (non-SolrCloud) mode with no authentication enabled, allowing unauthenticated configset file modifications that could introduce malicious <lib> tags.

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 9.8.0 or later
Fixed in 9.8.0
Interim mitigation

Enable authentication and authorization on Solr clusters, or upgrade to Solr 9.8.0+ which disables <lib> tags by default, or migrate to SolrCloud mode.

Recommended fix High confidence

Solr 9.8.0

  1. 1. Back up your current Solr configuration, data, and configsets
  2. 2. Download Apache Solr 9.8.0 from the official Apache Solr downloads page (https://solr.apache.org/downloads.html)
  3. 3. Stop the currently running Solr instance
  4. 4. Replace the existing Solr installation with version 9.8.0
  5. 5. Restore your backed-up configuration and data
  6. 6. Start the Solr 9.8.0 instance
  7. 7. Verify that Solr starts successfully and configsets load properly
  8. 8. If you rely on <lib> tags in configsets, review the new default behavior and enable them explicitly if needed (using the new configuration option)
Caveat Upgrading from 9.7 to 9.8.0 may affect configurations that use <lib> tags, as these are now disabled by default for security; verify that any required library loading still functions

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

Fix this in Solr Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24814 — 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-24814 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