dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-7291

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A weakness has been identified in o2oa up to 10.0. This affects the function FileAction of the file FileAction.java of the component URL Fetching. Executing a manipulation of the argument fileUrl can lead to server-side request forgery. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

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 · moderate confidence

Server-side request forgery (SSRF) vulnerability in o2oa's URL Fetching component (FileAction.java) allows remote attackers to manipulate the fileUrl parameter to make the server fetch arbitrary internal or external URLs, potentially accessing sensitive internal services or infrastructure.

MitigationImplement strict URL validation and allowlist controls for the fileUrl parameter to restrict fetching to approved domains and prevent requests to internal network addresses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 if o2oa is deployed
    Search for o2oa installation directories or running processes. Look for the 'o2oa' or 'o2server' process/service name, or check common installation paths like /opt/o2oa, /home/*/o2oa, or the application server hosting o2oa WAR files.
    Affected if o2oa server software is present in the environment
  2. Determine o2oa version
    Check the version file or manifest within the o2oa installation directory. Common locations include version.properties, about page in the web interface, or the build manifest file in the installation root.
    Affected if installed version falls within the vulnerable range (any unpatched version with the URL Fetching component)
  3. Verify URL Fetching component is accessible
    Locate FileAction.java or equivalent URL fetching endpoint in the deployed o2oa web application. Check if the /x_file_assemble_control servlet or similar URL-fetching endpoints are publicly or internally accessible.
    Affected if URL Fetching component (FileAction.java) is accessible without strict access controls
  4. Confirm lack of URL allowlist validation
    Inspect the FileAction.java source code or decompiled class for validation logic on the 'fileUrl' parameter. Search for URL validation functions, allowlist checks, or blacklist restrictions on the fileUrl parameter.
    Affected if No URL allowlist or strict validation is implemented on the fileUrl parameter before making requests
  5. Test for SSRF with internal URL
    If authorized, attempt a controlled request to an internal-only endpoint (such as localhost or an internal IP) via the fileUrl parameter to confirm the vulnerability exists. This should only be done in authorized testing environments.
    Affected if Server successfully fetches and responds with content from internal URLs (localhost, 127.0.0.1, internal network IPs) via the fileUrl parameter

Users are affected if o2oa with the URL Fetching component (FileAction.java) is deployed and the fileUrl parameter lacks strict allowlist validation, allowing arbitrary URL fetching.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation and allowlist controls for the fileUrl parameter to restrict fetching to approved domains and prevent requests to internal network addresses.

Have this fixed 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 help mitigating

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-7291 — 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-7291 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