dbcve.org
RollerApplication · Apache

CVE-2024-25090

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-26
Fix available
A fix is available. Upgrade to 6.1.3 or later.
See remediation →
58/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
Insufficient input validation and sanitation in Profile name & screenname, Bookmark name & description and blogroll name features in all versions of Apache Roller on all platforms allows an authenticated user to perform an XSS attack. Mitigation: if you do not have Roller configured for untrusted users, then you need to do nothing because you trust your users to author raw HTML and other web content. If you are running with untrusted users then you should upgrade to Roller 6.1.3. This issue affects Apache Roller: from 5.0.0 before 6.1.3. Users are recommended to upgrade to version 6.1.3, 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

Stored XSS vulnerability in Apache Roller's profile name, screenname, bookmark name/description, and blogroll name features due to insufficient input validation and sanitization. An authenticated user can inject malicious HTML/JavaScript through these fields that executes when other users view the affected data.

MitigationUpgrade to Apache Roller 6.1.3 which contains proper input validation. If the instance does not allow untrusted users, the risk is minimal as trusted users are expected to handle raw HTML content safely.

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
RollerApplication
Affected:>= 5.0.0, < 6.1.3

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Apache Roller version
    Locate the Roller version in the application administration UI (typically under About or System Info page), or inspect the deployed WAR file name/version. Check WEB-INF/lib for roller-core.jar and note its version.
    Affected if The installed version is 5.0.0 through 6.1.2 (inclusive), meaning it falls within >= 5.0.0 and < 6.1.3.
  2. Confirm user registration or public access is enabled
    Examine the Roller configuration or security settings to determine if self-registration is allowed for untrusted users, or if the blog/planet site is publicly accessible without authentication.
    Affected if Untrusted or unauthenticated users can register or access the Roller site, allowing them to view content created by authenticated users.
  3. Verify vulnerable profile fields are accessible
    Log in as a standard user (not admin) and navigate to the user profile settings. Check if the profile name and screenname fields are editable and can be saved.
    Affected if The profile name and screenname fields are editable and saved without sanitization, allowing stored XSS injection.
  4. Verify bookmark and blogroll features are accessible
    Navigate to the bookmarks or blogroll management section as an authenticated user. Check if you can add bookmarks with custom name/description or add blogroll entries with custom names.
    Affected if Bookmark name/description and blogroll name fields are editable and saved without proper input validation, creating stored XSS vectors.

You are affected if the installed Apache Roller version is 5.0.0 through 6.1.2 AND untrusted users can register or view content where profile name, screenname, bookmark, or blogroll data is displayed.

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

Upgrade to Apache Roller 6.1.3 which contains proper input validation. If the instance does not allow untrusted users, the risk is minimal as trusted users are expected to handle raw HTML content safely.

Recommended fix High confidence

6.1.3

  1. Backup your current Apache Roller installation and database before proceeding with the upgrade
  2. Download Apache Roller 6.1.3 from the official Apache download site (https://roller.apache.org/)
  3. Stop the running Roller application service
  4. Upgrade your Roller installation to version 6.1.3 following the standard upgrade procedure documented in the Apache Roller upgrade guide
  5. Start the Roller application service
  6. Verify the upgrade was successful by logging in and checking that Roller is functioning correctly
  7. Confirm the XSS vulnerability in Profile name, screenname, Bookmark name, description, and blogroll name features has been resolved
Caveat Test the upgrade in a non-production environment first; review release notes for any configuration or behavioral changes between your current version and 6.1.3

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

Fix this in Roller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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