AnswerApplication · Apache
CVE-2024-23349
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 Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache Answer.This issue affects Apache Answer: through 1.2.1. XSS attack when user enters summary. A logged-in user, when modifying their own submitted question, can input malicious code in the summary to create such an attack. Users are recommended to upgrade to version [1.2.5], 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 confidenceStored XSS vulnerability in Apache Answer where a logged-in user can inject malicious JavaScript code into the summary field when modifying their own question. The unsanitized input is stored and executed in the browsers of other users who view the question.
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
AnswerApplication
<= 1.2.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Apache Answer versionLocate the installed version through the admin dashboard (typically under Site Settings > About), API endpoint, or docker/container metadata. Compare against the affected range: <= 1.2.1Affected if Installed version is 1.2.1 or lower
-
Identify question summary fieldDetermine if questions in your Answer instance include a summary/description field. This is typically visible when creating or editing a question through the web UI or API.Affected if Questions support a summary or description field that accepts user input
-
Inspect database for XSS patternsQuery the questions table in the database (commonly named 'question' or similar) and examine the content of the summary/description field. Look for patterns like '<script', 'javascript:', 'onerror=', 'onload=' or other HTML/script tags that may indicate injected payloads.Affected if Any questions contain unsanitized script tags or event handlers in the summary field
-
Verify output encoding statusReview the rendering code or template files responsible for displaying question summaries. Check if the summary content is being HTML-encoded/escaped before output.Affected if Summary field content is rendered without proper HTML encoding or escaping
You are affected if Apache Answer version is 1.2.1 or lower AND questions with a summary field exist in your system that may contain unsanitized user-provided content.
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 · scopedUpgrade to version 1.2.5 which contains the fix. Additionally, implement proper output encoding/escaping for the summary field before rendering to prevent XSS.
1.2.5
- Backup your current Apache Answer installation and database
- Download Apache Answer version 1.2.5 from the official Apache Answer repository or releases page
- Stop the running Apache Answer service
- Replace the existing installation files with the new version 1.2.5 files
- Run any available database migration scripts if provided with the release
- Restart the Apache Answer service
- Verify the upgrade was successful by logging in and checking the version number
- Test the summary field in question editing to confirm the XSS vulnerability is fixed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Answer
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23349 — 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-2024-23349 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