dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-2731

CRITICAL · 10.0 CVSS v4.0 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Path traversal and content injection in JobRunnerBackground.aspx in DynamicWeb 8 (all) and 9 (<9.19.7 and <9.20.3) allows unauthenticated attackers to execute code via simple web requests

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

Path traversal and content injection vulnerability in JobRunnerBackground.aspx in DynamicWeb CMS allows unauthenticated remote code execution via simple HTTP requests. The vulnerability affects DynamicWeb 8 (all versions) and DynamicWeb 9 versions prior to 9.19.7 and 9.20.3.

MitigationApply vendor patch by upgrading to DynamicWeb 9.19.7+ or 9.20.3+. For DynamicWeb 8 (unpatched), implement network segmentation and WAF rules to block unauthorized access to JobRunnerBackground.aspx.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate JobRunnerBackground.aspx file
    Search the web server filesystem for the file JobRunnerBackground.aspx, typically found in the root or admin directory of the DynamicWeb CMS installation. Common paths include /Frontend/ or /Admin/ folders.
    Affected if The file exists in the web application directory and is accessible via HTTP.
  2. Identify DynamicWeb CMS version
    Check for a version file or assembly information in the DynamicWeb installation directory. Common locations include a version.txt, assemblyinfo, or the DLL files in the /bin folder. The version may also be displayed in the CMS admin interface under System or About pages.
    Affected if The installed version is DynamicWeb 8 (any version) OR DynamicWeb 9 versions below 9.19.7 or 9.20.3.
  3. Verify JobRunnerBackground.aspx is web-accessible
    Attempt a simple HTTP GET request to the JobRunnerBackground.aspx endpoint (for example: GET /JobRunnerBackground.aspx). Check if the server responds rather than returning a 404 or 403 error.
    Affected if The file responds to HTTP requests and is not blocked by authentication, IP restrictions, or other access controls.
  4. Check for content injection indicators
    Review web server access logs for unusual requests to JobRunnerBackground.aspx with path traversal patterns (such as ../ sequences) or suspicious query parameters that may indicate exploitation attempts.

A system is affected if JobRunnerBackground.aspx exists and is accessible, and the DynamicWeb version falls within 8.x (any) or 9.x below 9.19.7/9.20.3.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch by upgrading to DynamicWeb 9.19.7+ or 9.20.3+. For DynamicWeb 8 (unpatched), implement network segmentation and WAF rules to block unauthorized access to JobRunnerBackground.aspx.

Recommended fix High confidence

DynamicWeb 9.19.7 or later, or 9.20.3 or later (DynamicWeb 8.x users must migrate to 9.x)

  1. Identify the current DynamicWeb version by checking the installation or consulting system documentation
  2. If running DynamicWeb 8.x (all versions): Plan migration to DynamicWeb 9.x as version 8 is end-of-life and has no patch
  3. If running DynamicWeb 9.x: Upgrade to version 9.19.7 or later, or 9.20.3 or later (both contain the fix)
  4. Test the upgrade in a non-production environment before deploying to production
  5. Deploy the upgraded version to production
  6. Verify the JobRunnerBackground.aspx endpoint is no longer vulnerable to path traversal
Caveat DynamicWeb 8.x reaches end-of-life; migrating from 8.x to 9.x may require compatibility testing of custom integrations

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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