dbcve.org
Felix WebconsoleApplication · Apache

CVE-2025-25247

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-10
Fix available
A fix is available. Upgrade to 4.9.10 / 5.0.10 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache Felix Webconsole. This issue affects Apache Felix Webconsole 4.x up to 4.9.8 and 5.x up to 5.0.8. Users are recommended to upgrade to version 4.9.10 or 5.0.10 or higher, 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 confidence

Cross-site Scripting (XSS) vulnerability in Apache Felix Webconsole where improper input neutralization during web page generation allows injection of malicious scripts into web pages. This is a stored/reflected XSS affecting the admin web console interface.

MitigationUpgrade Apache Felix Webconsole to version 4.9.10 or 5.0.10 or higher. If immediate upgrade is not feasible, restrict network access to the webconsole endpoint or temporarily disable it.

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
Felix WebconsoleApplication
Affected:>= 4.0.0, < 4.9.10>= 5.0.0, < 5.0.10

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

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

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

  1. Locate Apache Felix Webconsole installation
    Search for the felix-webconsole JAR file or bundle in the application filesystem. Common paths include the OSGi bundle directory, lib folder, or embedded within a web application. Use commands like 'find / -name "*webconsole*.jar" 2>/dev/null' or check the OSGi bundle list if accessible.
    Affected if The Felix Webconsole bundle or JAR file is present in the environment
  2. Determine installed Webconsole version
    Inspect the version metadata of the found webconsole bundle. If using an OSGi framework, query the bundle version via the OSGi console or examine the MANIFEST.MF file inside the JAR. Compare the version number against the affected ranges: 4.0.0 to 4.9.9, or 5.0.0 to 5.0.9.
    Affected if The installed version falls within 4.0.0 to 4.9.9 OR 5.0.0 to 5.0.9
  3. Verify Webconsole HTTP endpoint is active
    Check if the web console HTTP service is running. Look for a web server listening on typical ports (such as 8080, 8443, or a configured port). Attempt to access the /system/console or /webconsole endpoint via HTTP GET to confirm the service responds.
    Affected if The web console endpoint responds to HTTP requests and is reachable on the network
  4. Confirm admin interface accessibility
    Determine if the web console is bound to a network interface other than localhost, or if authentication is disabled. Check the HTTP service configuration for the bind address setting. Attempt to access the console from an external host if network exposure is the concern.
    Affected if The admin console is network-accessible (not bound to 127.0.0.1 only) or allows unauthenticated access

The environment is affected if Apache Felix Webconsole versions 4.0.0-4.9.9 or 5.0.0-5.0.9 are installed AND the web console HTTP endpoint is active and accessible.

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 4.9.10 / 5.0.10 or later
Fixed in 4.9.105.0.10
Interim mitigation

Upgrade Apache Felix Webconsole to version 4.9.10 or 5.0.10 or higher. If immediate upgrade is not feasible, restrict network access to the webconsole endpoint or temporarily disable it.

Recommended fix High confidence

Upgrade to Felix Webconsole 4.9.10 (for 4.x users) or 5.0.10 (for 5.x users)

  1. 1. Identify the current version of Apache Felix Webconsole in use by checking the application's dependency management or bundle version
  2. 2. If using version 4.x (4.0.0 through 4.9.8), plan upgrade to version 4.9.10 or later; if using version 5.x (5.0.0 through 5.0.8), plan upgrade to version 5.0.10 or later
  3. 3. Update the Apache Felix Webconsole dependency in your project's pom.xml, package.json, or dependency management system to the target fixed version (4.9.10 or 5.0.10)
  4. 4. Rebuild the application with the updated dependency
  5. 5. Deploy the rebuilt application to your environment
  6. 6. Restart the application service
  7. 7. Verify the webconsole is accessible and functioning normally after the upgrade
Caveat Minor version upgrades within the same major branch (4.x to 4.9.10 or 5.x to 5.0.10) should have minimal breaking changes; however, review release notes for any behavior changes

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

Fix this in Felix Webconsole Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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