dbcve.org
AnswerApplication · Apache

CVE-2026-34031

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 2.0.1 or later.
See remediation →
74/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
Unrestricted Upload of File with Dangerous Type vulnerability in Apache Answer. This issue affects Apache Answer: through 2.0.0. The server did not sufficiently validate user-supplied image URLs, allowing arbitrary external content to be embedded as profile images, which could expose users to unintended external requests and tracking by third-party servers. 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

Apache Answer through 2.0.0 lacks proper validation on user-supplied image URLs for profile pictures. Attackers can embed arbitrary external URLs as profile images, causing the server and other users to make requests to attacker-controlled third-party servers, enabling tracking and potential SSRF-like attacks.

MitigationUpgrade to Apache Answer version 2.0.1 which implements proper validation of user-supplied image URLs to restrict embedding to trusted sources only.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
    Look for the 'answer' service/process running on the server, or check common installation directories such as /opt/answer, /var/www/answer, or Docker containers named 'answer'. Also check port 80/443 for the Answer web interface.
    Affected if Apache Answer is found running on the system
  2. Determine installed version
    Check the version by logging into the admin dashboard and navigating to 'System > About', or by inspecting the version file in the installation directory (often version.txt or similar), or query the API endpoint /api/v1/health if available.
    Affected if The version displayed is lower than 2.0.1 (for example, 2.0.0, 1.x.x, or any version < 2.0.1)
  3. Verify profile picture feature accessibility
    Log in as a regular authenticated user (non-admin), navigate to user profile settings, and confirm that an option exists to set a profile picture from an external URL.
    Affected if The profile settings allow entering custom image URLs from external sources

A user is affected if Apache Answer version is below 2.0.1 and the profile picture feature allowing external URLs is accessible to authenticated users.

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 to Apache Answer version 2.0.1 which implements proper validation of user-supplied image URLs to restrict embedding to trusted sources only.

Recommended fix High confidence

2.0.1

  1. 1. Back up your existing Apache Answer data and configuration files.
  2. 2. Stop the currently running Apache Answer service.
  3. 3. Upgrade Apache Answer to version 2.0.1 using your installation method (e.g., Docker, binary, or package manager).
  4. 4. Restart the Apache Answer service.
  5. 5. Verify the upgrade was successful by logging in and checking the profile image functionality works correctly with properly validated URLs.

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

Fix this in Answer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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