Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4772

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-02

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

58/100

Remediation priority · Elevated

Remotely reachable 7 weeks old

Official description

NVD · unedited

Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in TR7 Cyber Defense Inc. WAF-ASP allows Stored XSS. This issue affects WAF-ASP: from v1.0.324.900 before v1.4.0.117.

Technical summary

dbcve analysis · moderate confidence

Stored XSS vulnerability in TR7 Cyber Defense Inc. WAF-ASP allows attackers to inject malicious scripts through unsanitized input that gets stored and rendered to other users. The flaw exists due to improper neutralization of input during web page generation in versions v1.0.324.900 through v1.4.0.116.

MitigationUpgrade WAF-ASP to v1.4.0.117 or later which contains the fix. If immediate upgrade is not possible, implement additional input validation and output encoding at the application layer as a compensating control.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm WAF-ASP installation

Locate and identify the TR7 Cyber Defense Inc. WAF-ASP installation in your environment. Check for the product name in installed software, services, or documentation.

Affected if WAF-ASP from TR7 Cyber Defense Inc. is not present in the environment
Determine installed version

Access the WAF-ASP administrative interface or check the product installation directory for version information. Common methods include: logging into the admin dashboard and viewing 'About' or 'System Info' pages, or checking version files in the installation directory.

Affected if The installed version is v1.0.324.900, v1.4.0.116, or any version in between (e.g., v1.2.0.500, v1.3.5.200)
Verify web interface is accessible

Confirm that the WAF-ASP web management interface is accessible to users or administrators. Attempt to reach the login page or API endpoints.

Affected if The web interface is exposed and accepts user input in any feature
Identify user input functionality

Review the WAF-ASP web interface for features that accept and store user-provided data such as policy names, rule descriptions, custom signatures, or configuration labels.

Affected if Any feature stores user-supplied input that is later displayed to other users without sanitization

The environment is affected if the installed WAF-ASP version falls within the range v1.0.324.900 through v1.4.0.116 and the web interface with user input functionality is enabled.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade WAF-ASP to v1.4.0.117 or later which contains the fix. If immediate upgrade is not possible, implement additional input validation and output encoding at the application layer as a compensating control.

Recommended fix Moderate confidence

v1.4.0.117 or later

1. Check the current installed version of WAF-ASP to confirm it falls within the affected range (v1.0.324.900 to v1.4.0.116)
2. Create a complete backup of the current WAF-ASP configuration and any associated data
3. Download the fixed version v1.4.0.117 or later from the official vendor (TR7 Cyber Defense Inc.)
4. Follow the vendor's documented upgrade procedure to install the fixed version
5. After upgrade, verify the new version is correctly installed
6. Test that the XSS vulnerability is no longer present by attempting to inject stored XSS payloads through the affected input fields
7. Monitor for any issues after the upgrade

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

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

siberguvenlik.gov.tr
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4772 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-4772?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.1%

Remediation

Need this fixed?

Have this fixed 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-4772 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References