FortiwebApplication · Fortinet
CVE-2012-6346
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in FortiWeb before 4.4.4 allow remote attackers to inject arbitrary web script or HTML via the (1) redir or (2) mkey parameter to waf/pcre_expression/validate.
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 confidenceMultiple reflected cross-site scripting (XSS) vulnerabilities in FortiWeb web application firewall product, affecting the waf/pcre_expression/validate endpoint. The redir and mkey parameters do not properly sanitize user input before reflecting it back in the HTTP response, allowing injection of arbitrary JavaScript or HTML.
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
FortiwebApplication
< 4.4.4CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiWeb installationAccess the FortiWeb web management interface or use CLI command 'get system status' to confirm FortiWeb is runningAffected if The target system is FortiWeb web application firewall
-
Check installed FortiWeb versionIn the web UI, navigate to System > Status or use CLI command 'get system status' to view the firmware versionAffected if The displayed version number is lower than 4.4.4 (for example, 4.4.3, 4.4.2, etc.)
-
Confirm vulnerable endpoint existsAttempt to access the URL path /waf/pcre_expression/validate on the FortiWeb management interface or the protected web applicationAffected if The endpoint responds with any HTTP status (200, 404, or redirect)
-
Test redir parameter for reflectionSend an HTTP request to /waf/pcre_expression/validate with a test value in the redir parameter (such as redir=test123) and examine if the value appears unmodified in the response bodyAffected if The redir parameter value is reflected in the response without proper HTML encoding
-
Test mkey parameter for reflectionSend an HTTP request to /waf/pcre_expression/validate with a test value in the mkey parameter and examine the HTTP responseAffected if The mkey parameter value appears in the response unescaped or unencoded
The environment is affected if FortiWeb version is below 4.4.4 AND the waf/pcre_expression/validate endpoint reflects the redir or mkey parameters without sanitization in the HTTP response.
Generated from the published advisory. Verify against your own configuration.
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 data4.4.4
Upgrade FortiWeb to version 4.4.4 or later, which contains the fix for this vulnerability. Alternatively, implement input validation and output encoding on the vulnerable parameters.
Fix this in Fortiweb
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-6346 in production — separate from our analysis above.
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.
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.
- 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