dbcve.org
Felix Http Webconsole PluginPlugin / extension · Apache

CVE-2025-27867

MEDIUM · 5.6 CVSS v3.1 Published 2025-03-12
Fix available
A fix is available. Upgrade to 1.2.2 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache Felix HTTP Webconsole Plugin. This issue affects Apache Felix HTTP Webconsole Plugin: from Version 1.X through 1.2.0. Users are recommended to upgrade to version 1.2.2, 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 HTTP Webconsole Plugin allows attackers to inject malicious scripts through unsanitized input during web page generation. The vulnerability affects versions 1.X through 1.2.0 and is fixed in version 1.2.2.

MitigationUpgrade Apache Felix HTTP Webconsole Plugin to version 1.2.2 or later to remediate the XSS vulnerability.

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 Http Webconsole PluginPlugin / extension
Affected:>= 1.0.0, < 1.2.2

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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. Identify installed version of Apache Felix HTTP Webconsole Plugin
    Query the OSGi container for the bundle version using the Felix shell or Web Console status page. Check the bundle manifest for Bundle-Version header, or use the OSGi console command 'bundle <id>' to inspect the Apache Felix HTTP Webconsole Plugin bundle.
    Affected if installed version is 1.0.0 through 1.2.1 (versions less than 1.2.2)
  2. Confirm the webconsole plugin is deployed and active
    Check the OSGi container for bundles in ACTIVE state related to Apache Felix Http and Web Console. Look for http bundle and webconsole plugin bundle in the bundle list.
    Affected if the Apache Felix HTTP Webconsole bundle is installed and in ACTIVE state
  3. Verify HTTP endpoint accessibility
    Determine if the webconsole is accessible over HTTP by checking the HTTP service port configuration and any firewall or network exposure settings. The webconsole is typically accessible at /system/console.
    Affected if the webconsole HTTP endpoint is reachable from a network where potential attackers could deliver XSS payloads
  4. Check for unauthenticated or low-privilege access paths
    Review the security configuration for the webconsole plugin to determine if authentication is enforced. Examine the JAAS or other auth configuration files for the HTTP service.
    Affected if the webconsole allows unauthenticated access or permits users with limited privileges to access plugin functions that generate pages with unsanitized input

A user is affected if the Apache Felix HTTP Webconsole Plugin version is 1.0.0 through 1.2.1 AND the webconsole is accessible over HTTP to users who could trigger the XSS vulnerability through unsanitized input fields.

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

Upgrade Apache Felix HTTP Webconsole Plugin to version 1.2.2 or later to remediate the XSS vulnerability.

Recommended fix High confidence

1.2.2

  1. Identify the current version of Apache Felix HTTP Webconsole Plugin in your environment
  2. Stop the application or service that uses the Felix HTTP Webconsole Plugin
  3. Upgrade the Apache Felix HTTP Webconsole Plugin from your current version to version 1.2.2
  4. After upgrading, verify the plugin version is correctly reported as 1.2.2
  5. Restart the application or service
  6. Verify the webconsole is accessible and functioning properly

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

Fix this in Felix Http Webconsole Plugin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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