dbcve.org
AnswerApplication · Apache

CVE-2026-25699

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 2.0.1 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
Exposure of Private Personal Information to an Unauthorized Actor vulnerability in Apache Answer. This issue affects Apache Answer: through 2.0.0. Timeline-related APIs lacked proper authorization checks, allowing regular authenticated users to access deleted, private, or unapproved content and its revision history. Users are recommended to upgrade to version 2.0.1, 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

Timeline-related APIs in Apache Answer versions through 2.0.0 lacked proper authorization checks, allowing authenticated (but non-privileged) users to access deleted, private, or unapproved content and its revision history, exposing private personal information.

MitigationUpgrade Apache Answer to version 2.0.1 which contains the fix for proper authorization enforcement on timeline APIs.

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.1

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. Identify Apache Answer installation
    Check if Apache Answer is deployed in your environment by looking for answer-related processes, services, or web applications running on common ports (usually port 80/443 or configured ports).
    Affected if Apache Answer is present and running in the environment.
  2. Determine installed version
    Locate the version file or check the application metadata. Common approaches: check the Docker image tag, look for version information in the application admin panel, or inspect the binary/package version if self-hosted.
    Affected if The running version is anything less than 2.0.1.
  3. Verify timeline API accessibility
    Test whether timeline-related API endpoints are accessible to authenticated users. Attempt to access content in deleted, private, or unapproved states through the timeline APIs using a standard authenticated user account.
    Affected if Timeline APIs return restricted content (deleted, private, or unapproved content) or revision history that should not be accessible to regular authenticated users.
  4. Confirm authorization gaps exist
    Compare API responses for timeline endpoints against expected behavior. Check if authenticated users can view revision history or access content that should be hidden based on content status (deleted, private, unapproved).
    Affected if Timeline APIs expose private personal information through unrestricted access to protected content states.

You are affected if Apache Answer version is below 2.0.1 and timeline APIs are accessible to authenticated users without proper authorization controls on restricted content.

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.1 or later
Fixed in 2.0.1
Interim mitigation

Upgrade Apache Answer to version 2.0.1 which contains the fix for proper authorization enforcement on timeline APIs.

Recommended fix High confidence

2.0.1

  1. Backup your current Answer installation and database before upgrading.
  2. Download Apache Answer version 2.0.1 from the official Apache Answer repository or releases page.
  3. Stop the running Answer service.
  4. Replace the existing Answer files with the new version 2.0.1 files.
  5. Review any configuration changes required for version 2.0.1 by comparing your existing configuration with the new version's default configuration.
  6. Start the Answer service.
  7. Verify the application is running correctly and test that timeline-related APIs now enforce proper authorization.

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

Fix this in Answer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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