dbcve.org
AnswerApplication · Apache

CVE-2026-24735

HIGH · 7.5 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
84/100
Remediation priority · High
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
Exposure of Private Personal Information to an Unauthorized Actor vulnerability in Apache Answer. This issue affects Apache Answer: through 1.7.1. An unauthenticated API endpoint incorrectly exposes full revision history for deleted content. This allows unauthorized user to retrieve restricted or sensitive information. Users are recommended to upgrade to version 2.0.0, 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

An unauthenticated API endpoint in Apache Answer versions through 1.7.1 incorrectly exposes the full revision history for deleted content, allowing unauthorized actors to retrieve sensitive or restricted information without any authentication.

MitigationUpgrade Apache Answer to version 2.0.0 or later to remediate this 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
AnswerApplication
Affected:< 2.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Answer installation
    Locate the Answer application directory or running service. Check for files like answer, answer.service, or Docker containers named answer. Look for the typical installation path /opt/answer or check running processes for the answer binary.
    Affected if Apache Answer software is present in the environment
  2. Determine installed version
    Check the version file or executable version flag. Common methods: run 'answer version' if CLI available, check version displayed in the web UI footer, or inspect the binary/docker image tag. Compare against the affected range of versions < 2.0.0.
    Affected if Installed version is any release prior to 2.0.0 (versions through 1.7.1 are confirmed affected)
  3. Locate the API endpoint documentation or routes
    Review the API documentation or examine the source code routes. Look for endpoints related to content revision history, specifically those handling deleted content. Common patterns include endpoints with 'revision', 'history', 'deleted', or 'content' in the path.
    Affected if The revision history endpoint for deleted content exists in the codebase and is accessible via API
  4. Test unauthenticated access to deleted content revisions
    Send an HTTP request to the suspected revision history API endpoint for deleted content items without providing any authentication credentials. Use a tool like curl: curl -s -w '%{http_code}' http://<server>/api/v1/revision/<deleted_content_id> or similar path pattern. Observe if the full revision history is returned with HTTP 200.
    Affected if The endpoint returns full revision history data without requiring authentication (HTTP 200 response with sensitive content)
  5. Verify the API lacks authorization checks
    Examine the API handler code for the revision endpoint. Confirm there is no middleware, decorator, or code path that enforces user authentication or authorization before returning deleted content revision data. Check for absence of session validation or token verification in the relevant controller.
    Affected if The API handler contains no authentication or authorization checks before exposing deleted content revision history

If Apache Answer version is below 2.0.0 and the deleted content revision history API endpoint is accessible without authentication credentials, the environment is affected by this CVE.

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

Upgrade Apache Answer to version 2.0.0 or later to remediate this vulnerability.

Recommended fix High confidence

2.0.0

  1. Backup your current Apache Answer installation and database
  2. Download Apache Answer version 2.0.0 from the official Apache Answer repository
  3. Upgrade your Apache Answer installation to version 2.0.0
  4. Verify the upgrade was successful and test that the API endpoint no longer exposes revision history for deleted content

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

Fix this in Answer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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