CWE-352
Weakness AllowedCross-Site Request Forgery
Abstraction: Compound · Status: Stable
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Mapping guidance
This is a well-known Composite of multiple weaknesses that must all occur simultaneously, although it is attack-oriented in nature.
While attack-oriented composites are supported in CWE, they have not been a focus of research. There is a chance that future research or CWE scope clarifications will change or deprecate them. Perform root-cause analysis to determine if other weaknesses allow CSRF attacks to occur, and map to those weaknesses. For example, predictable CSRF tokens might allow bypass of CSRF protection mechanisms; if this occurs, they might be better characterized as randomness/predictability weaknesses.
Relationships and members
Modes of introduction
REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Detection methods
Manual Analysis
This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session.
Specifically, manual analysis can be useful for finding this weakness, and for minimizing false positives assuming an understanding of business logic. However, it might not achieve desired code coverage within limited time constraints. For black-box analysis, if credentials are not known for privileged accounts, then the most security-critical portions of the application may not receive sufficient attention.
Consider using OWASP CSRFTester to identify potential issues and aid in manual analysis.
Effectiveness: High
These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.
Automated Static Analysis
CSRF is currently difficult to detect reliably using automated techniques. This is because each application has its own implicit security policy that dictates which requests can be influenced by an outsider and automatically performed on behalf of a user, versus which requests require strong confidence that the user intends to make the request. For example, a keyword search of the public portion of a web site is typically expected to be encoded within a link that can be launched automatically when the user clicks on the link.
Effectiveness: Limited
Automated Static Analysis - Binary or Bytecode
According to SOAR [REF-1479], the following detection techniques may be useful:
Cost effective for partial coverage:
Bytecode Weakness Analysis - including disassembler + source code weakness analysis
Binary Weakness Analysis - including disassembler + source code weakness analysis
Effectiveness: SOAR Partial
Manual Static Analysis - Binary or Bytecode
According to SOAR [REF-1479], the following detection techniques may be useful:
Cost effective for partial coverage:
Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies
Effectiveness: SOAR Partial
Dynamic Analysis with Automated Results Interpretation
According to SOAR [REF-1479], the following detection techniques may be useful:
Highly cost effective:
Web Application Scanner
Effectiveness: High
Dynamic Analysis with Manual Results Interpretation
According to SOAR [REF-1479], the following detection techniques may be useful:
Highly cost effective:
Fuzz Tester
Framework-based Fuzzer
Effectiveness: High
Manual Static Analysis - Source Code
According to SOAR [REF-1479], the following detection techniques may be useful:
Cost effective for partial coverage:
Focused Manual Spotcheck - Focused manual analysis of source
Manual Source Code Review (not inspections)
Effectiveness: SOAR Partial
Automated Static Analysis - Source Code
According to SOAR [REF-1479], the following detection techniques may be useful:
Cost effective for partial coverage:
Source code Weakness Analyzer
Context-configured Source Code Weakness Analyzer
Effectiveness: SOAR Partial
Architecture or Design Review
According to SOAR [REF-1479], the following detection techniques may be useful:
Cost effective for partial coverage:
Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)
Formal Methods / Correct-By-Construction
Effectiveness: SOAR Partial
Notes
Relationship
There can be a close relationship between XSS and CSRF (CWE-352). An attacker might use CSRF in order to trick the victim into submitting requests to the server in which the requests contain an XSS payload. A well-known example of this was the Samy worm on MySpace [REF-956]. The worm used XSS to insert malicious HTML sequences into a user's profile and add the attacker as a MySpace friend. MySpace friends of that victim would then execute the payload to modify their own profiles, causing the worm to propagate exponentially. Since the victims did not intentionally insert the malicious script themselves, CSRF was a root cause.
Theoretical
The CSRF topology is multi-channel:
Attacker (as outsider) to intermediary (as user). The interaction point is either an external or internal channel.
Intermediary (as user) to server (as victim). The activation point is an internal channel.
Content history
Contributed usability diagram concepts used by the CWE team.
updated Time_of_Introduction
updated Alternate_Terms, Description, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings
updated Applicable_Platforms, Description, Likelihood_of_Exploit, Observed_Examples, Other_Notes, Potential_Mitigations, References, Relationship_Notes, Relationships, Research_Gaps, Theoretical_Notes
updated Potential_Mitigations
Added demonstrative example for profile.
updated Demonstrative_Examples, Related_Attack_Patterns
updated Common_Consequences, Demonstrative_Examples, Detection_Factors, Likelihood_of_Exploit, Observed_Examples, Potential_Mitigations, Time_of_Introduction
updated Applicable_Platforms, Detection_Factors, References, Relationships, Taxonomy_Mappings
updated Common_Consequences, Detection_Factors, Potential_Mitigations, References, Relationships
updated Potential_Mitigations
updated Description
updated Common_Consequences
updated Relationships
updated Potential_Mitigations, References
updated Related_Attack_Patterns, Relationships
updated Potential_Mitigations
updated Relationships
updated References, Relationships
updated Detection_Factors
updated Relationships
updated Applicable_Platforms, Likelihood_of_Exploit, Modes_of_Introduction, References, Relationships
updated References, Relationship_Notes, Research_Gaps
updated Relationships
updated Relationships
updated Relationships, Theoretical_Notes
updated Relationships
updated Relationships
updated Relationships
updated Relationships
updated References, Relationships
updated Mapping_Notes, Relationships
updated Relationships
updated Alternate_Terms, Common_Consequences, Description, Diagram
updated Detection_Factors, Potential_Mitigations, References
updated Applicable_Platforms, Relationships, Weakness_Ordinalities
updated Applicable_Platforms, Name, References, Relationships, Taxonomy_Mappings
15161 vulnerabilities reference this CWE, most recent first.
CVE-2026-134449 (GCVE-0-2026-134449)
Vulnerability from cvelistv5 – Published: 2026-11-21 16:32 – Updated: 2026-11-21 16:32- CWE-352 - Cross-Site Request Forgery (CSRF)
| URL | Tags |
|---|---|
| https://github.com/Finsys/dockhand/security/advis… | vendor-advisory |
| https://www.vulncheck.com/advisories/dockhand-bef… | third-party-advisory |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "dockhand",
"vendor": "Finsys",
"versions": [
{
"lessThan": "1.0.57",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "1.0.57",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "vinniboy021-blip"
}
],
"datePublic": "2026-11-04T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Dockhand before 1.0.57 contains a cross-site request forgery vulnerability that allows attackers to perform state-changing actions by exploiting missing Origin header validation and absent CSRF tokens. Attackers can lure authenticated users to a same-site attacker page that submits forged POST requests to stop, start, or delete stacks, modify settings, and change credentials."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "HIGH"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 6.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-21T16:32:59.530Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-c7r9-g9c5-xc8f)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/Finsys/dockhand/security/advisories/GHSA-c7r9-g9c5-xc8f"
},
{
"name": "VulnCheck Advisory: Dockhand before 1.0.57 Cross-Site Request Forgery via Missing Origin Validation",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/dockhand-before-1.0.57-cross-site-request-forgery-via-missing-origin-validation"
}
],
"title": "Dockhand before 1.0.57 Cross-Site Request Forgery via Missing Origin Validation",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-134449",
"datePublished": "2026-11-21T16:32:59.530Z",
"dateReserved": "2026-11-21T00:09:00.772Z",
"dateUpdated": "2026-11-21T16:32:59.530Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-134398 (GCVE-0-2026-134398)
Vulnerability from cvelistv5 – Published: 2026-11-21 16:33 – Updated: 2026-11-21 16:33- CWE-352 - Cross-Site Request Forgery (CSRF)
| URL | Tags |
|---|---|
| https://github.com/frappe/erpnext/security/adviso… | vendor-advisory |
| https://www.vulncheck.com/advisories/frappe-erpne… | third-party-advisory |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "erpnext",
"vendor": "frappe",
"versions": [
{
"lessThan": "15.121.4",
"status": "affected",
"version": "15.87.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "15.121.4",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"product": "erpnext",
"vendor": "frappe",
"versions": [
{
"lessThan": "16.36.0",
"status": "affected",
"version": "16.0.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "16.36.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:frappe:erpnext:*:*:*:*:*:*:*:*",
"versionEndExcluding": "15.121.4",
"versionStartIncluding": "15.87.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
},
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:frappe:erpnext:*:*:*:*:*:*:*:*",
"versionEndExcluding": "16.36.0",
"versionStartIncluding": "16.0.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "joostgrunwald"
},
{
"lang": "en",
"type": "remediation developer",
"value": "diptanilsaha"
}
],
"datePublic": "2026-11-06T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Frappe ERPNext 15.87.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an Accounts module endpoint that changes Period Closing Voucher job status without permission checks and accepts a request method triggerable cross-site. Authenticated users without an Accounts role, or cross-site pages opened by authenticated users, can send requests naming a scheduled job to stop accounting jobs from completing."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-21T16:33:42.972Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-93gm-m6q2-39pc)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/frappe/erpnext/security/advisories/GHSA-93gm-m6q2-39pc"
},
{
"name": "VulnCheck Advisory: Frappe ERPNext 15.87.0 before 15.121.4 Missing Authorization in Period Closing Voucher Status",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/frappe-erpnext-15.87.0-before-15.121.4-missing-authorization-in-period-closing-voucher-status"
}
],
"title": "Frappe ERPNext 15.87.0 before 15.121.4 Missing Authorization in Period Closing Voucher Status",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-134398",
"datePublished": "2026-11-21T16:33:42.972Z",
"dateReserved": "2026-11-21T00:04:18.249Z",
"dateUpdated": "2026-11-21T16:33:42.972Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-134362 (GCVE-0-2026-134362)
Vulnerability from cvelistv5 – Published: 2026-11-21 16:34 – Updated: 2026-11-21 16:34- CWE-352 - Cross-Site Request Forgery (CSRF)
| URL | Tags |
|---|---|
| https://github.com/coder/coder/security/advisorie… | vendor-advisory |
| https://www.vulncheck.com/advisories/coder-from-2… | third-party-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| coder | coder |
Affected:
2.38.0 , < 2.38.6
(semver)
Unaffected: 2.38.6 (semver) |
|
| coder | coder |
Affected:
2.37.0 , < 2.37.10
(semver)
Unaffected: 2.37.10 (semver) |
|
| coder | coder |
Affected:
2.30.0 , < 2.34.18
(semver)
Unaffected: 2.34.18 (semver) |
|
| coder | coder |
Affected:
2.6.0 , < 2.29.26
(semver)
Unaffected: 2.29.26 (semver) |
|
| coder | coder |
Affected:
2.35.0 , < 2.37.0
(semver)
|
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:golang/github.com/coder/coder/v2",
"product": "coder",
"vendor": "coder",
"versions": [
{
"lessThan": "2.38.6",
"status": "affected",
"version": "2.38.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2.38.6",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"packageURL": "pkg:golang/github.com/coder/coder/v2",
"product": "coder",
"vendor": "coder",
"versions": [
{
"lessThan": "2.37.10",
"status": "affected",
"version": "2.37.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2.37.10",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"packageURL": "pkg:golang/github.com/coder/coder/v2",
"product": "coder",
"vendor": "coder",
"versions": [
{
"lessThan": "2.34.18",
"status": "affected",
"version": "2.30.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2.34.18",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"packageURL": "pkg:golang/github.com/coder/coder/v2",
"product": "coder",
"vendor": "coder",
"versions": [
{
"lessThan": "2.29.26",
"status": "affected",
"version": "2.6.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2.29.26",
"versionType": "semver"
}
]
},
{
"defaultStatus": "unaffected",
"packageURL": "pkg:golang/github.com/coder/coder/v2",
"product": "coder",
"vendor": "coder",
"versions": [
{
"lessThan": "2.37.0",
"status": "affected",
"version": "2.35.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:coder:coder:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.38.6",
"versionStartIncluding": "2.38.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:coder:coder:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.37.10",
"versionStartIncluding": "2.37.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:coder:coder:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.34.18",
"versionStartIncluding": "2.30.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:coder:coder:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.29.26",
"versionStartIncluding": "2.6.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:coder:coder:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.37.0",
"versionStartIncluding": "2.35.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "remediation developer",
"value": "BobbyHo"
}
],
"datePublic": "2026-11-04T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Coder 2.6.0 before 2.29.26, 2.30.0 before 2.34.18, 2.35.0 before 2.37.10, and 2.38.0 before 2.38.6 contains a cross-site request forgery vulnerability because CSRF exemption patterns in coderd/httpmw/csrf.go are matched as unanchored regular expressions, letting affected API routes skip CSRF token and same-origin checks. Attackers controlling a page same-site with the deployment can make signed-in users\u0027 browsers send forged POST requests that recreate dev containers or add users whose names contain derp to organizations."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 2.3,
"baseSeverity": "LOW",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "LOW",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 4.2,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-21T16:34:18.933Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-jvgx-787p-cfmg)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/coder/coder/security/advisories/GHSA-jvgx-787p-cfmg"
},
{
"name": "VulnCheck Advisory: Coder from 2.38.0 before 2.38.6 CSRF Bypass via Unanchored Exemption Patterns",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/coder-from-2.38.0-before-2.38.6-csrf-bypass-via-unanchored-exemption-patterns"
}
],
"title": "Coder from 2.38.0 before 2.38.6 CSRF Bypass via Unanchored Exemption Patterns",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-134362",
"datePublished": "2026-11-21T16:34:18.933Z",
"dateReserved": "2026-11-21T00:01:23.102Z",
"dateUpdated": "2026-11-21T16:34:18.933Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-134279 (GCVE-0-2026-134279)
Vulnerability from cvelistv5 – Published: 2026-11-21 16:35 – Updated: 2026-11-21 16:35- CWE-352 - Cross-Site Request Forgery (CSRF)
| URL | Tags |
|---|---|
| https://github.com/go-vikunja/vikunja/security/ad… | vendor-advisory |
| https://www.vulncheck.com/advisories/vikunja-from… | third-party-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| go-vikunja | vikunja |
Affected:
0.20.5 , < 2.8.0
(semver)
Unaffected: 2.8.0 (semver) cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:golang/code.vikunja.io/api",
"product": "vikunja",
"vendor": "go-vikunja",
"versions": [
{
"lessThan": "2.8.0",
"status": "affected",
"version": "0.20.5",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "2.8.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.8.0",
"versionStartIncluding": "0.20.5",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"datePublic": "2026-11-05T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Vikunja from 0.20.5 before 2.8.0 contains a login cross-site request forgery vulnerability in the OpenID Connect callback in OpenIdAuth.vue that accepts a valueless state parameter. Attackers can send a crafted callback link with an empty state and their own authorization code to silently log victims into the attacker\u0027s account and view the victims\u0027 entered data."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 2.3,
"baseSeverity": "LOW",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.2,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-21T16:35:25.452Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-597v-7qmv-777g)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-597v-7qmv-777g"
},
{
"name": "VulnCheck Advisory: Vikunja from 0.20.5 before 2.8.0 Login CSRF via OIDC Callback State Check",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/vikunja-from-0.20.5-before-2.8.0-login-csrf-via-oidc-callback-state-check"
}
],
"title": "Vikunja from 0.20.5 before 2.8.0 Login CSRF via OIDC Callback State Check",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-134279",
"datePublished": "2026-11-21T16:35:25.452Z",
"dateReserved": "2026-11-20T23:47:55.597Z",
"dateUpdated": "2026-11-21T16:35:25.452Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133651 (GCVE-0-2026-133651)
Vulnerability from cvelistv5 – Published: 2026-11-20 10:24 – Updated: 2026-11-20 18:23- CWE-352 - Cross-Site Request Forgery (CSRF)
| URL | Tags |
|---|---|
| https://github.com/flowintel/flowintel/commit/c29… | patch |
qwen3.8:27b
2 events
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-20 10:16 - Model
qwen3.8:27b- Input
-
https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.patch
8d58806814d8… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
c29a27c4973f
|
fix: [security] Require CSRF-protected POST for destructive | 8d58806814d8… |
Fix summary
The vulnerability is remediated by restricting all fourteen affected web routes to accept only POST requests, ensuring that Flask-WTF's CSRF token validation is enforced. All fifteen client-side callers (JavaScript fetch calls and HTML template scripts) were updated to send POST requests with the page's CSRF token in the X-CSRFToken header, preserving legitimate user interactions while blocking cross-site forged requests.
Patch summary
Backend: Changed the methods parameter on fourteen Flask route decorators from methods=['GET'] or methods=['GET','POST'] to methods=['POST'] across app/admin/admin.py, app/case/case.py, app/case/task.py, app/connectors/connectors.py, app/custom_tags/custom_tags.py, app/templating/templating.py, and app/tools/tools.py. Frontend: Updated fifteen fetch() calls in JavaScript files and HTML templates to include method: 'POST' and headers: {'X-CSRFToken': $('#csrf_token').val()}. No changes to permission decorators, query parameters, or API-key-authenticated routes.
CVSS rationale
AV:N - exploit is over the network via a web browser. AC:L - crafting a link or page that triggers a GET request is trivial. AT:N - no attack target manipulation beyond the victim's browser. PR:N - the attacker requires no account; the victim's existing session is used. UI:A - the victim must actively navigate to or click a crafted link (commit message references 'cross-site navigation'). VC:N, VI:N, VA:N - no direct impact on the application's own confidentiality, integrity, or availability. SC:N, SI:H, SA:N - the impact is on the integrity of the victim's data (deletion/modification of cases, tasks, templates, connectors, tags, taxonomies, galaxies) with no cross-system impact.
Weakness rationale
- CWE-352 The routes accepted GET requests, which are not subject to Flask-WTF's CSRF token check. This allowed a cross-site navigation to invoke destructive state-changing operations using the victim's authenticated session, a textbook CSRF scenario.
Attack pattern rationale
- CAPEC-124 The attack pattern involves an attacker crafting a request (in this case a GET navigation) that is sent to the target application using the victim's authenticated session cookie, causing the application to perform an unintended state-changing action. This is the closest and most direct CAPEC match for a GET-based CSRF bypass of token validation.
Assumptions to verify
- The affected_version '0' from explicit context is treated as a placeholder indicating all versions prior to 4.1.0; the exact earliest affected version is not specified in the patch.
- UI:A is selected based on the commit message referencing 'cross-site navigation'; if an attacker could use a passive vector (e.g., an auto-loading image tag), UI could be P, but the evidence specifically describes navigation.
- PR:N assumes the attacker does not need their own account; the victim's authenticated session is sufficient. If the application requires the victim to have editor or admin role, this is a precondition on the victim, not a privilege requirement for the attacker.
- CAPEC-124 is the closest standard mapping; no more specific CAPEC exists for GET-based CSRF bypass of framework token validation.
- The patch does not indicate whether the CSRF token was previously absent from the page or only not enforced on GET; the fix implies the token was available in the DOM but the GET method bypassed validation.
Model comparison
Selected qwen3.8:27b
by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.
| Model | Score | Agreement | Confidence | Assumptions |
|---|---|---|---|---|
qwen3.8:27b |
8 | 11 | high | 5 |
- 2026-11-02 14:03 UTC Fix developed Corrective change authored (c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc): fix: [security] Require CSRF-protected POST for destructive https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.patch
- 2026-11-20 10:15 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.patch
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133651",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T18:23:00.226813Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T18:23:19.024Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
],
"modules": [
"app/admin/admin.py",
"app/case/case.py",
"app/case/task.py",
"app/connectors/connectors.py",
"app/custom_tags/custom_tags.py",
"app/templating/templating.py",
"app/tools/tools.py"
],
"product": "flowintel",
"programFiles": [],
"repo": "https://github.com/flowintel/flowintel",
"vendor": "flowintel",
"versions": [
{
"lessThan": "4.1.0",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"descriptions": [
{
"lang": "en",
"value": "FlowIntel contained a Cross-Site Request Forgery (CSRF) vulnerability affecting fourteen web routes that performed destructive or state-changing operations. The affected routes accepted HTTP GET requests in addition to (or instead of) POST, which bypassed the Flask-WTF CSRF token validation that is only enforced on non-GET requests.\n\nThe vulnerable operations included:\n- Case deletion and case merging\n- Organisation removal from a case\n- Task deletion (case and template)\n- Case template and note template deletion\n- Connector, connector instance, and icon deletion\n- Custom tag deletion and status change\n- Taxonomy and galaxy status changes\n\nAn attacker who could induce an authenticated user to follow a crafted link or load a page containing a cross-site navigation (e.g., an image tag or redirect) could trigger any of these destructive actions using the victim\u0027s session cookie, without the victim\u0027s explicit consent or awareness. No special privileges beyond a valid authenticated session with the appropriate role (editor or admin) were required on the victim\u0027s account.\n\nSecurity impact: unauthorized deletion or modification of cases, tasks, templates, connectors, icons, custom tags, taxonomies, and galaxies belonging to the victim or the organisation, resulting in loss of data integrity.\n\nAffected versions: FlowIntel prior to 4.1.0"
}
],
"impacts": [
{
"capecId": "CAPEC-124",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-124 Cross-Site Request Forgery"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "HIGH",
"userInteraction": "ACTIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T10:16:24Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "CWE-352 Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T10:24:17.885Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc"
}
],
"solutions": [
{
"lang": "en",
"value": "The vulnerability is remediated by restricting all fourteen affected web routes to accept only POST requests, ensuring that Flask-WTF\u0027s CSRF token validation is enforced. All fifteen client-side callers (JavaScript fetch calls and HTML template scripts) were updated to send POST requests with the page\u0027s CSRF token in the X-CSRFToken header, preserving legitimate user interactions while blocking cross-site forged requests."
}
],
"title": "FlowIntel CSRF via GET-accepted destructive web routes bypassing Flask-WTF protection",
"x_gcve": [
{
"extensions": {
"bcp-05-x-01": {
"ai_annotations": [
{
"ai_level": "generated",
"description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
"gna_source": 1,
"models": [
{
"gna_source": 1,
"identifier": "qwen3.8:27b",
"name": "qwen3.8:27b",
"source": "ollama"
}
],
"review_status": "full",
"scope": "record",
"tags": [
"ai-computer-assisted:llm-generated",
"ai-computer-assisted:classification"
]
}
]
},
"bcp-05-x-02": {
"x_patch2vuln": {
"assumptions": [
"The affected_version \u00270\u0027 from explicit context is treated as a placeholder indicating all versions prior to 4.1.0; the exact earliest affected version is not specified in the patch.",
"UI:A is selected based on the commit message referencing \u0027cross-site navigation\u0027; if an attacker could use a passive vector (e.g., an auto-loading image tag), UI could be P, but the evidence specifically describes navigation.",
"PR:N assumes the attacker does not need their own account; the victim\u0027s authenticated session is sufficient. If the application requires the victim to have editor or admin role, this is a precondition on the victim, not a privilege requirement for the attacker.",
"CAPEC-124 is the closest standard mapping; no more specific CAPEC exists for GET-based CSRF bypass of framework token validation.",
"The patch does not indicate whether the CSRF token was previously absent from the page or only not enforced on GET; the fix implies the token was available in the DOM but the GET method bypassed validation."
],
"capecRationale": [
{
"capecId": "CAPEC-124",
"rationale": "The attack pattern involves an attacker crafting a request (in this case a GET navigation) that is sent to the target application using the victim\u0027s authenticated session cookie, causing the application to perform an unintended state-changing action. This is the closest and most direct CAPEC match for a GET-based CSRF bypass of token validation."
}
],
"commit": "c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "elhoim"
},
{
"lang": "en",
"type": "remediation developer",
"value": "David Cruciani"
}
],
"cvssRationale": "AV:N - exploit is over the network via a web browser. AC:L - crafting a link or page that triggers a GET request is trivial. AT:N - no attack target manipulation beyond the victim\u0027s browser. PR:N - the attacker requires no account; the victim\u0027s existing session is used. UI:A - the victim must actively navigate to or click a crafted link (commit message references \u0027cross-site navigation\u0027). VC:N, VI:N, VA:N - no direct impact on the application\u0027s own confidentiality, integrity, or availability. SC:N, SI:H, SA:N - the impact is on the integrity of the victim\u0027s data (deletion/modification of cases, tasks, templates, connectors, tags, taxonomies, galaxies) with no cross-system impact.",
"fixSummary": "The vulnerability is remediated by restricting all fourteen affected web routes to accept only POST requests, ensuring that Flask-WTF\u0027s CSRF token validation is enforced. All fifteen client-side callers (JavaScript fetch calls and HTML template scripts) were updated to send POST requests with the page\u0027s CSRF token in the X-CSRFToken header, preserving legitimate user interactions while blocking cross-site forged requests.",
"generatedAt": "2026-11-20T10:16:24.400257Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 5,
"confidence": "high",
"model": "qwen3.8:27b",
"score": 8
}
],
"selectedModel": "qwen3.8:27b",
"selectionMethod": "deterministic-consensus-v1",
"selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
},
"patchSha256": "8d58806814d8ac1f104c7206ff3b4c2e842c8a0c94205dcf816813439ac98863",
"patchSummary": "Backend: Changed the methods parameter on fourteen Flask route decorators from methods=[\u0027GET\u0027] or methods=[\u0027GET\u0027,\u0027POST\u0027] to methods=[\u0027POST\u0027] across app/admin/admin.py, app/case/case.py, app/case/task.py, app/connectors/connectors.py, app/custom_tags/custom_tags.py, app/templating/templating.py, and app/tools/tools.py. Frontend: Updated fifteen fetch() calls in JavaScript files and HTML templates to include method: \u0027POST\u0027 and headers: {\u0027X-CSRFToken\u0027: $(\u0027#csrf_token\u0027).val()}. No changes to permission decorators, query parameters, or API-key-authenticated routes.",
"patchTruncated": false,
"patches": [
{
"commit": "c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc",
"date": "Mon, 2 Nov 2026 15:03:14 +0100",
"patchSha256": "8d58806814d8ac1f104c7206ff3b4c2e842c8a0c94205dcf816813439ac98863",
"retrievedAt": "2026-11-20T10:15:57.346441Z",
"source": "https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.patch",
"sourceUrl": "https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.patch",
"subject": "fix: [security] Require CSRF-protected POST for destructive"
}
],
"source": "https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T10:16:24Z",
"version": "2.0.3"
},
"subject": "fix: [security] Require CSRF-protected POST for destructive",
"weaknessRationale": [
{
"cweId": "CWE-352",
"rationale": "The routes accepted GET requests, which are not subject to Flask-WTF\u0027s CSRF token check. This allowed a cross-site navigation to invoke destructive state-changing operations using the victim\u0027s authenticated session, a textbook CSRF scenario."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"events": [
{
"description": "Corrective change authored (c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc): fix: [security] Require CSRF-protected POST for destructive",
"id": "evt-fix-developed-1",
"references": [
"https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.patch"
],
"timestamp": "2026-11-02T14:03:14Z",
"type": "fix-developed"
},
{
"description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
"id": "evt-fix-available-1",
"references": [
"https://github.com/flowintel/flowintel/commit/c29a27c4973f0e47cb235cdfbeb8743bd11a3bbc.patch"
],
"timestamp": "2026-11-20T10:15:57.346441Z",
"type": "fix-available"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "GCVE-1-2026-20237"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133651",
"datePublished": "2026-11-20T10:24:17.885Z",
"dateReserved": "2026-11-20T10:24:15.465Z",
"dateUpdated": "2026-11-20T18:23:19.024Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133611 (GCVE-0-2026-133611)
Vulnerability from cvelistv5 – Published: 2026-11-20 07:17 – Updated: 2026-11-20 17:17| URL | Tags |
|---|---|
| https://github.com/vulnerability-lookup/vulnerabi… | patch |
| Vendor | Product | Version | |
|---|---|---|---|
| vulnerability-lookup | vulnerability-lookup |
Affected:
<7.1.0 , < 7.1.0
(semver)
cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:* |
qwen3.8:27b
5 events
Fix in 2 days
advisory
bcp-05-x-01bcp-05-x-02bcp-05-x-03
Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.
| Model | Source | Identifier |
|---|---|---|
| qwen3.8:27b | ollama | qwen3.8:27b |
- Generator
-
patch2vuln.pyon 2026-11-20 07:07 - Model
qwen3.8:27b- Input
-
https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766.patch
3641069d834b… - Confidence
- high
| Commit | Subject | Patch SHA-256 |
|---|---|---|
3c8d6c27a8a9
|
fix: [user] Disabling 2FA needs a POST and the password | 3641069d834b… |
Fix summary
The /user/toggle_2fa endpoint is restricted to POST only, enabling CSRF token validation, and now requires the user's password to confirm disabling of 2FA. The comment detail view now checks the comment's publication status and returns 404 for unpublished comments unless the requester is the author or holds moderator privileges, matching the existing API behavior.
Patch summary
In website/web/views/user.py, the route decorator for toggle_2FA is changed from methods=["GET"] to methods=["POST"], and a password verification block (request.form.get("password") with current_user.check_password) is added before the 2FA flag is cleared. In website/web/templates/user/edit_user.html, the disable-2FA link is replaced with a modal form that submits a POST with a CSRF token and a password field; the enable-2FA link is converted to a POST form with a hidden csrf_token input. In website/web/views/comment.py, an authorization check is added after the comment lookup: if the comment is unpublished and the current user is neither the author (can_user_edit_comment) nor a moderator (can_user_manage_comment with comment:publish), the view aborts with 404. A new test file tests/test_toggle_2fa.py covers GET rejection, missing/wrong password rejection, successful password-confirmed disable, CSRF token enforcement, and unpublished comment visibility for anonymous users, other users, and the author.
CVSS rationale
AV:N: the attack is delivered over the network via a web page. AC:L: the attack is straightforward (embed an image tag in a comment). AT:P: the attacker passively injects content (a comment with a crafted image) into the application. PR:L: the attacker needs a basic user account to create a comment. UI:P: the victim passively interacts by viewing the comment page. VC/VI/VA:N: the web application itself is not directly compromised in confidentiality, integrity, or availability. SC:N: no confidentiality impact on other systems. SI:H: the victim's 2FA is disabled, a significant integrity impact on the user's account security posture. SA:N: no administrative impact. The comment visibility issue is a secondary finding and does not elevate the primary vector.
Weakness rationale
- CWE-352 The 2FA disable endpoint accepted GET requests, allowing a state-changing operation to be triggered by an image tag or link in user-supplied content without a CSRF token. This is a textbook CSRF vulnerability where the HTTP method and lack of anti-CSRF protection on a sensitive action enable cross-site request forgery.
- CWE-306 Disabling two-factor authentication is a critical security action that did not require re-authentication (password confirmation). The endpoint performed the sensitive operation with only a session cookie, without verifying the user's password, weakening the authentication boundary.
- CWE-862 The comment detail web view did not check the comment's publication status or the viewer's role before rendering the content. Unpublished comments were accessible to any user (or anonymous visitor) who knew the UUID, bypassing the authorization model enforced by the API.
Attack pattern rationale
- CAPEC-123 The patch explicitly describes the attack: an image in a comment pointing at /user/toggle_2fa disabled the viewer's second factor. This is a direct CSRF pattern where a GET request to a state-changing endpoint is triggered by the victim's browser while viewing attacker-controlled content. The fix (POST-only + CSRF token + password) confirms the CSRF classification.
- CAPEC-126 The unpublished comment was accessible to anyone who knew or guessed the UUID in the URL, without an authorization check on publication status. This maps to insecure direct object reference / broken access control. Note: the exact CAPEC-126 name may vary in the official catalog; this is the closest available pattern for authorization bypass through a user-controlled resource identifier. Uncertainty exists in the precise CAPEC identifier mapping for this secondary finding.
Assumptions to verify
- The CAPEC-126 mapping for the unpublished comment authorization bypass is the closest available pattern; the exact CAPEC identifier for 'broken access control via direct object reference' may differ in the official catalog. Uncertainty noted.
- CVSS AT:P assumes the attacker passively injects content (a comment with a crafted image) into the application; if the attacker must actively manipulate the victim's session, AT could be reconsidered.
- CVSS PR:L assumes the attacker needs only a basic user account to create a comment; if comment creation is open to anonymous users, PR could be N.
- CVSS UI:P assumes the victim passively views a page; if the victim must actively click a link, UI could be A.
- The comment visibility issue is treated as a secondary finding within the same advisory per the patch set assumption; it does not independently elevate the CVSS vector.
- The affected version range (<7.1.0) is taken from the explicit analyst context; the patch itself does not enumerate all prior affected versions.
- The ENFORCE_2FA configuration flag being false is a precondition for the 2FA disable attack; on instances where 2FA is enforced, the disable path is blocked.
Model comparison
Selected qwen3.8:27b
by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.
| Model | Score | Agreement | Confidence | Assumptions |
|---|---|---|---|---|
qwen3.8:27b |
6 | 11 | high | 7 |
- Report to fix
- 2 days (reported 2026-11-18 06:04 UTC → fix available 2026-11-20 07:00 UTC)
- 2026-11-18 06:04 UTC Reported reporter Reported privately through GitHub private vulnerability reporting (GHSA-vvwj-x8f5-rf69): GET /user/toggle_2fa disables the logged-in user's 2FA without a CSRF token or password, and can be triggered by an image in a comment. https://github.com/vulnerability-lookup/vulnerability-lookup/security/advisories/GHSA-vvwj-x8f5-rf69
- 2026-11-20 Validated coordinator Reproduced on a local instance with ENFORCE_2FA off. Triage also found that the page of an unpublished comment was readable by anyone with its link, so the attack did not depend on moderation.
- 2026-11-20 06:50 UTC Fix developed maintainer Corrective change authored (3c8d6c27a8a93e532567f3c4949c437d8db37766): /user/toggle_2fa is POST only and asks for the password; unpublished comments are shown only to their author and to moderators. https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766
- 2026-11-20 07:00 UTC Fix available maintainer Vulnerability-Lookup 7.1.0 released: the fix and the signed tag v7.1.0 pushed to the public repository. https://github.com/vulnerability-lookup/vulnerability-lookup/releases/tag/v7.1.0 https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766
- 2026-11-20 07:07 UTC Identifier assigned gna GCVE-1-2026-20335 assigned when the draft record was generated by Patch2Vuln.
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133611",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T17:17:18.094135Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T17:17:28.235Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [
"cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*"
],
"modules": [
"website/web/views/user.py",
"website/web/views/comment.py",
"website/web/templates/user/edit_user.html"
],
"product": "vulnerability-lookup",
"programFiles": [],
"repo": "https://github.com/vulnerability-lookup/vulnerability-lookup",
"vendor": "vulnerability-lookup",
"versions": [
{
"lessThan": "7.1.0",
"status": "affected",
"version": "\u003c7.1.0",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "@orshih6"
},
{
"lang": "en",
"type": "remediation developer",
"value": "C\u00e9dric Bonhomme"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "coordinator",
"value": "C\u00e9dric Bonhomme"
}
],
"descriptions": [
{
"lang": "en",
"value": "vulnerability-lookup prior to version 7.1.0 contains two security issues in its web interface. First, the /user/toggle_2fa endpoint accepted HTTP GET requests and disabled the authenticated user\u0027s two-factor authentication without requiring password confirmation. Because the state-changing operation was reachable via GET, an attacker with a basic account could embed an image element (or any other GET-triggering markup) in a comment pointing to that endpoint. When a victim with 2FA enabled viewed the comment, their browser silently issued the GET request, disabling the victim\u0027s second factor of authentication. No CSRF token was enforced on the GET path, and no password was required to confirm the action. Second, the comment detail page (/comment/\u003cuuid\u003e) rendered unpublished comments to any visitor who possessed the URL, bypassing the moderation workflow that was intended to keep such content hidden until approved. The API correctly restricted access, but the web view did not enforce the same authorization check. The combined effect allows an attacker to degrade a victim\u0027s account security (removal of 2FA) through a single page view and to read content that was not yet approved for public release."
}
],
"impacts": [
{
"capecId": "CAPEC-123",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-123 Cross-Site Request Forgery (CSRF)"
}
]
},
{
"capecId": "CAPEC-126",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-126 Exploiting Insecure Direct Object References"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 4.6,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "HIGH",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
},
{
"format": "SSVC",
"other": {
"content": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T07:07:57Z",
"version": "2.0.3"
},
"type": "SSVC"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "CWE-352 Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306 Missing Authentication for Critical Function",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-862",
"description": "CWE-862 Missing Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T07:17:33.474Z",
"orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"shortName": "CIRCL"
},
"references": [
{
"name": "Security patch",
"tags": [
"patch"
],
"url": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766"
}
],
"solutions": [
{
"lang": "en",
"value": "The /user/toggle_2fa endpoint is restricted to POST only, enabling CSRF token validation, and now requires the user\u0027s password to confirm disabling of 2FA. The comment detail view now checks the comment\u0027s publication status and returns 404 for unpublished comments unless the requester is the author or holds moderator privileges, matching the existing API behavior."
}
],
"title": "vulnerability-lookup: 2FA Disabled via Unauthenticated GET Request and Unpublished Comments Accessible Without Authorization",
"x_gcve": [
{
"extensions": {
"bcp-05-x-01": {
"ai_annotations": [
{
"ai_level": "generated",
"description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
"gna_source": 1,
"models": [
{
"gna_source": 1,
"identifier": "qwen3.8:27b",
"name": "qwen3.8:27b",
"source": "ollama"
}
],
"review_status": "full",
"scope": "record",
"tags": [
"ai-computer-assisted:llm-generated",
"ai-computer-assisted:classification"
]
}
]
},
"bcp-05-x-02": {
"x_patch2vuln": {
"assumptions": [
"The CAPEC-126 mapping for the unpublished comment authorization bypass is the closest available pattern; the exact CAPEC identifier for \u0027broken access control via direct object reference\u0027 may differ in the official catalog. Uncertainty noted.",
"CVSS AT:P assumes the attacker passively injects content (a comment with a crafted image) into the application; if the attacker must actively manipulate the victim\u0027s session, AT could be reconsidered.",
"CVSS PR:L assumes the attacker needs only a basic user account to create a comment; if comment creation is open to anonymous users, PR could be N.",
"CVSS UI:P assumes the victim passively views a page; if the victim must actively click a link, UI could be A.",
"The comment visibility issue is treated as a secondary finding within the same advisory per the patch set assumption; it does not independently elevate the CVSS vector.",
"The affected version range (\u003c7.1.0) is taken from the explicit analyst context; the patch itself does not enumerate all prior affected versions.",
"The ENFORCE_2FA configuration flag being false is a precondition for the 2FA disable attack; on instances where 2FA is enforced, the disable path is blocked."
],
"capecRationale": [
{
"capecId": "CAPEC-123",
"rationale": "The patch explicitly describes the attack: an image in a comment pointing at /user/toggle_2fa disabled the viewer\u0027s second factor. This is a direct CSRF pattern where a GET request to a state-changing endpoint is triggered by the victim\u0027s browser while viewing attacker-controlled content. The fix (POST-only + CSRF token + password) confirms the CSRF classification."
},
{
"capecId": "CAPEC-126",
"rationale": "The unpublished comment was accessible to anyone who knew or guessed the UUID in the URL, without an authorization check on publication status. This maps to insecure direct object reference / broken access control. Note: the exact CAPEC-126 name may vary in the official catalog; this is the closest available pattern for authorization bypass through a user-controlled resource identifier. Uncertainty exists in the precise CAPEC identifier mapping for this secondary finding."
}
],
"commit": "3c8d6c27a8a93e532567f3c4949c437d8db37766",
"confidence": "high",
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "@orshih6"
},
{
"lang": "en",
"type": "remediation developer",
"value": "C\u00e9dric Bonhomme"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Claude Opus 5.5"
},
{
"lang": "en",
"type": "coordinator",
"value": "C\u00e9dric Bonhomme"
}
],
"cvssRationale": "AV:N: the attack is delivered over the network via a web page. AC:L: the attack is straightforward (embed an image tag in a comment). AT:P: the attacker passively injects content (a comment with a crafted image) into the application. PR:L: the attacker needs a basic user account to create a comment. UI:P: the victim passively interacts by viewing the comment page. VC/VI/VA:N: the web application itself is not directly compromised in confidentiality, integrity, or availability. SC:N: no confidentiality impact on other systems. SI:H: the victim\u0027s 2FA is disabled, a significant integrity impact on the user\u0027s account security posture. SA:N: no administrative impact. The comment visibility issue is a secondary finding and does not elevate the primary vector.",
"draft": false,
"fixSummary": "The /user/toggle_2fa endpoint is restricted to POST only, enabling CSRF token validation, and now requires the user\u0027s password to confirm disabling of 2FA. The comment detail view now checks the comment\u0027s publication status and returns 404 for unpublished comments unless the requester is the author or holds moderator privileges, matching the existing API behavior.",
"generatedAt": "2026-11-20T07:07:57.871769Z",
"generator": "patch2vuln.py",
"model": "qwen3.8:27b",
"modelComparison": {
"potentialErrors": [],
"rankings": [
{
"agreementScore": 11,
"assumptionCount": 7,
"confidence": "high",
"model": "qwen3.8:27b",
"score": 6
}
],
"selectedModel": "qwen3.8:27b",
"selectionMethod": "deterministic-consensus-v1",
"selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
},
"patchSha256": "3641069d834b039cfac95ec2aee7e8b361aa9393154da118f94bf2b95cbf4085",
"patchSummary": "In website/web/views/user.py, the route decorator for toggle_2FA is changed from methods=[\"GET\"] to methods=[\"POST\"], and a password verification block (request.form.get(\"password\") with current_user.check_password) is added before the 2FA flag is cleared. In website/web/templates/user/edit_user.html, the disable-2FA link is replaced with a modal form that submits a POST with a CSRF token and a password field; the enable-2FA link is converted to a POST form with a hidden csrf_token input. In website/web/views/comment.py, an authorization check is added after the comment lookup: if the comment is unpublished and the current user is neither the author (can_user_edit_comment) nor a moderator (can_user_manage_comment with comment:publish), the view aborts with 404. A new test file tests/test_toggle_2fa.py covers GET rejection, missing/wrong password rejection, successful password-confirmed disable, CSRF token enforcement, and unpublished comment visibility for anonymous users, other users, and the author.",
"patchTruncated": false,
"patches": [
{
"commit": "3c8d6c27a8a93e532567f3c4949c437d8db37766",
"date": "Fri, 20 Nov 2026 07:50:40 +0100",
"patchSha256": "3641069d834b039cfac95ec2aee7e8b361aa9393154da118f94bf2b95cbf4085",
"retrievedAt": "2026-11-20T07:06:43.921059Z",
"source": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766.patch",
"sourceUrl": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766.patch",
"subject": "fix: [user] Disabling 2FA needs a POST and the password"
}
],
"source": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766.patch",
"ssvc": {
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "Supplier",
"timestamp": "2026-11-20T07:07:57Z",
"version": "2.0.3"
},
"subject": "fix: [user] Disabling 2FA needs a POST and the password",
"weaknessRationale": [
{
"cweId": "CWE-352",
"rationale": "The 2FA disable endpoint accepted GET requests, allowing a state-changing operation to be triggered by an image tag or link in user-supplied content without a CSRF token. This is a textbook CSRF vulnerability where the HTTP method and lack of anti-CSRF protection on a sensitive action enable cross-site request forgery."
},
{
"cweId": "CWE-306",
"rationale": "Disabling two-factor authentication is a critical security action that did not require re-authentication (password confirmation). The endpoint performed the sensitive operation with only a session cookie, without verifying the user\u0027s password, weakening the authentication boundary."
},
{
"cweId": "CWE-862",
"rationale": "The comment detail web view did not check the comment\u0027s publication status or the viewer\u0027s role before rendering the content. Unpublished comments were accessible to any user (or anonymous visitor) who knew the UUID, bypassing the authorization model enforced by the API."
}
]
}
},
"bcp-05-x-03": {
"x_timeline": {
"entities": [
{
"category": "discoverer",
"id": "reporter",
"name": "@orshih6",
"references": [
"https://github.com/orshih6"
]
},
{
"category": "vendor",
"id": "vulnerability-lookup",
"name": "Vulnerability-Lookup",
"references": [
"https://github.com/vulnerability-lookup/vulnerability-lookup"
]
},
{
"category": "coordinator",
"id": "coordinator",
"name": "C\u00e9dric Bonhomme"
}
],
"events": [
{
"actor": "reporter",
"actorRefs": [
"reporter"
],
"description": "Reported privately through GitHub private vulnerability reporting (GHSA-vvwj-x8f5-rf69): GET /user/toggle_2fa disables the logged-in user\u0027s 2FA without a CSRF token or password, and can be triggered by an image in a comment.",
"id": "evt-reported-1",
"recipientRefs": [
"vulnerability-lookup"
],
"references": [
"https://github.com/vulnerability-lookup/vulnerability-lookup/security/advisories/GHSA-vvwj-x8f5-rf69"
],
"timestamp": "2026-11-18T06:04:28Z",
"type": "reported"
},
{
"actor": "coordinator",
"actorRefs": [
"coordinator"
],
"description": "Reproduced on a local instance with ENFORCE_2FA off. Triage also found that the page of an unpublished comment was readable by anyone with its link, so the attack did not depend on moderation.",
"id": "evt-validated-1",
"referencedEvents": [
"evt-reported-1"
],
"timestamp": "2026-11-20",
"type": "validated"
},
{
"actor": "maintainer",
"actorRefs": [
"coordinator"
],
"description": "Corrective change authored (3c8d6c27a8a93e532567f3c4949c437d8db37766): /user/toggle_2fa is POST only and asks for the password; unpublished comments are shown only to their author and to moderators.",
"id": "evt-fix-developed-1",
"referencedEvents": [
"evt-validated-1"
],
"references": [
"https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766"
],
"timestamp": "2026-11-20T06:50:40Z",
"type": "fix-developed"
},
{
"actor": "maintainer",
"actorRefs": [
"vulnerability-lookup"
],
"description": "Vulnerability-Lookup 7.1.0 released: the fix and the signed tag v7.1.0 pushed to the public repository.",
"id": "evt-fix-available-1",
"referencedEvents": [
"evt-fix-developed-1"
],
"references": [
"https://github.com/vulnerability-lookup/vulnerability-lookup/releases/tag/v7.1.0",
"https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3c8d6c27a8a93e532567f3c4949c437d8db37766"
],
"timestamp": "2026-11-20T07:00:52Z",
"type": "fix-available"
},
{
"actor": "gna",
"actorRefs": [
"vulnerability-lookup"
],
"description": "GCVE-1-2026-20335 assigned when the draft record was generated by Patch2Vuln.",
"id": "evt-identifier-assigned-1",
"referencedEvents": [
"evt-fix-available-1"
],
"timestamp": "2026-11-20T07:07:57Z",
"type": "identifier-assigned"
}
]
}
}
},
"recordType": "advisory",
"vulnId": "gcve-1-2026-20335"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
"assignerShortName": "CIRCL",
"cveId": "CVE-2026-133611",
"datePublished": "2026-11-20T07:17:33.474Z",
"dateReserved": "2026-11-20T07:17:22.792Z",
"dateUpdated": "2026-11-20T17:17:28.235Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-133112 (GCVE-0-2026-133112)
Vulnerability from cvelistv5 – Published: 2026-11-19 13:54 – Updated: 2026-11-19 15:53- CWE-352 - Cross-Site Request Forgery (CSRF)
| URL | Tags |
|---|---|
| https://github.com/modified-shop/modified-shop/is… | issue-tracking |
| https://github.com/capivara-research/modified-sho… | technical-description |
| https://github.com/modified-shop/modified-shop/bl… | technical-description |
| https://github.com/modified-shop/modified-shop | product |
| https://www.vulncheck.com/advisories/modified-eco… | third-party-advisory |
| Vendor | Product | Version | |
|---|---|---|---|
| modified-shop | modified-shop |
Affected:
0 , ≤ 3.3.0
(custom)
cpe:2.3:a:modified-shop:modified_ecommerce_shopsoftware:*:*:*:*:*:*:*:* |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133112",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T15:46:26.157889Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T15:53:40.737Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:github/modified-shop/modified-shop",
"product": "modified-shop",
"repo": "https://github.com/modified-shop/modified-shop",
"vendor": "modified-shop",
"versions": [
{
"lessThanOrEqual": "3.3.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:modified-shop:modified_ecommerce_shopsoftware:*:*:*:*:*:*:*:*",
"versionEndIncluding": "3.3.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Fernando Viana"
},
{
"lang": "en",
"type": "finder",
"value": "Marcus Chaves"
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "modified eCommerce Shopsoftware through 3.3.0 contains a cross-site request forgery vulnerability in gv_send.php because the action=process step never validates a CSRF token via check_secure_form(). Attackers can host an auto-submitting form that makes a logged-in customer send their gift voucher balance to an attacker-controlled email address for redemption."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "HIGH",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 2.3,
"baseSeverity": "LOW",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 3.1,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T13:54:34.953Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/modified-shop/modified-shop/issues/3772"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/capivara-research/modified-shop-csrf-gv-send"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/modified-shop/modified-shop/blob/c531afbf7279f6e60ca7cda09f2c9d7ca5305c46/gv_send.php#L88-L159"
},
{
"tags": [
"product"
],
"url": "https://github.com/modified-shop/modified-shop"
},
{
"name": "VulnCheck Advisory: modified eCommerce Shopsoftware through 3.3.0 CSRF via gv_send.php",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/modified-ecommerce-shopsoftware-through-3.3.0-csrf-via-gv-send-php"
}
],
"title": "modified eCommerce Shopsoftware through 3.3.0 CSRF via gv_send.php",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-133112",
"datePublished": "2026-11-19T13:54:34.953Z",
"dateReserved": "2026-11-19T12:25:22.746Z",
"dateUpdated": "2026-11-19T15:53:40.737Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131716 (GCVE-0-2026-131716)
Vulnerability from cvelistv5 – Published: 2026-11-20 08:59 – Updated: 2026-11-20 19:45 X_Open Source- CWE-352 - Cross-Site Request Forgery (CSRF)
| URL | Tags |
|---|---|
| https://patchstack.com/database/wordpress/plugin/… | vdb-entry |
| Vendor | Product | Version | |
|---|---|---|---|
| Awesomemotive | Charitable |
Affected:
0 , ≤ 1.8.15.1
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131716",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T19:26:44.962331Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T19:45:51.973Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://wordpress.org/plugins",
"defaultStatus": "unaffected",
"packageName": "charitable",
"product": "Charitable",
"vendor": "Awesomemotive",
"versions": [
{
"changes": [
{
"at": "1.8.15.2",
"status": "unaffected"
}
],
"lessThanOrEqual": "1.8.15.1",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "AndrewN | Patchstack Bug Bounty Program"
}
],
"datePublic": "2026-11-20T08:59:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Cross-Site Request Forgery (CSRF) vulnerability in Awesomemotive Charitable charitable allows Cross Site Request Forgery.\u003cp\u003eThis issue affects Charitable: from n/a through 1.8.15.1.\u003c/p\u003e"
}
],
"value": "Cross-Site Request Forgery (CSRF) vulnerability in Awesomemotive Charitable charitable allows Cross Site Request Forgery.This issue affects Charitable: from n/a through 1.8.15.1."
}
],
"impacts": [
{
"capecId": "CAPEC-62",
"descriptions": [
{
"lang": "en",
"value": "Cross Site Request Forgery"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T08:59:19.742Z",
"orgId": "21595511-bba5-4825-b968-b78d1f9984a3",
"shortName": "Patchstack"
},
"references": [
{
"tags": [
"vdb-entry"
],
"url": "https://patchstack.com/database/wordpress/plugin/charitable/vulnerability/wordpress-charitable-plugin-1-8-15-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cve"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Update the WordPress Charitable plugin to the latest available version (at least 1.8.15.2)."
}
],
"value": "Update the WordPress Charitable plugin to the latest available version (at least 1.8.15.2)."
}
],
"tags": [
"x_open-source"
],
"title": "WordPress Charitable plugin \u003c= 1.8.15.1 - Cross Site Request Forgery (CSRF) vulnerability"
}
},
"cveMetadata": {
"assignerOrgId": "21595511-bba5-4825-b968-b78d1f9984a3",
"assignerShortName": "Patchstack",
"cveId": "CVE-2026-131716",
"datePublished": "2026-11-20T08:59:17.659Z",
"dateReserved": "2026-11-17T22:26:30.761Z",
"dateUpdated": "2026-11-20T19:45:51.973Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-131188 (GCVE-0-2026-131188)
Vulnerability from cvelistv5 – Published: 2026-11-19 19:55 – Updated: 2026-11-20 04:57- CWE-352 - The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.
| Vendor | Product | Version | |
|---|---|---|---|
| Splunk | Splunk Enterprise |
Affected:
10.4 , < 10.4.4
(custom)
Affected: 10.2 , < 10.2.8 (custom) Affected: 10.0 , < 10.0.11 (custom) Affected: 9.4 , < 9.4.16 (custom) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-131188",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-19T00:00:00+00:00",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T04:57:15.898Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"modules": [
"Splunk Web"
],
"product": "Splunk Enterprise",
"vendor": "Splunk",
"versions": [
{
"lessThan": "10.4.4",
"status": "affected",
"version": "10.4",
"versionType": "custom"
},
{
"lessThan": "10.2.8",
"status": "affected",
"version": "10.2",
"versionType": "custom"
},
{
"lessThan": "10.0.11",
"status": "affected",
"version": "10.0",
"versionType": "custom"
},
{
"lessThan": "9.4.16",
"status": "affected",
"version": "9.4",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-18T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could craft a malicious link that, if opened by an authenticated user, executes arbitrary Search Processing Language (SPL) searches with the victim\u0027s permissions. \nSuccessful exploitation could allow the unauthenticated user to access or modify data, alter Splunk platform configurations, and disrupt operations available to the affected user.\nThe vulnerability is possible because the Portable Document Format (PDF) generation component processes request data before it rejects deprecated GET requests and does not apply SPL safeguards for risky commands to subsearches.\nFor more information see Generate PDFs of your reports and dashboards (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/10.4/report-management/generate-pdfs-of-your-reports-and-dashboards) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.1,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.",
"lang": "en",
"type": "cwe"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-19T19:55:36.832Z",
"orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"shortName": "cisco"
},
"references": [
{
"url": "https://advisory.splunk.com/advisories/SVD-2026-1103"
}
],
"solutions": [
{
"lang": "en",
"value": "Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher."
}
],
"source": {
"advisory": "SVD-2026-1103",
"discovery": ""
},
"title": "SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Portable Document Format (PDF) Generation in Splunk Enterprise",
"workarounds": [
{
"lang": "en",
"value": "The vulnerability affects instances with Splunk Web turned on. Turning Splunk Web off is a possible workaround.\nSee [Disable unnecessary Splunk Enterprise components](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/install-splunk-enterprise-securely/disable-unnecessary-splunk-enterprise-components) and the [web.conf](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/configuration-file-reference/10.2.0-configuration-file-reference/web.conf) configuration specification file for more information on turning off Splunk Web."
}
]
}
},
"cveMetadata": {
"assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
"assignerShortName": "cisco",
"cveId": "CVE-2026-131188",
"datePublished": "2026-11-19T19:55:36.832Z",
"dateReserved": "2026-11-17T20:26:14.301Z",
"dateUpdated": "2026-11-20T04:57:15.898Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-129945 (GCVE-0-2026-129945)
Vulnerability from cvelistv5 – Published: 2026-11-16 15:06 – Updated: 2026-11-16 17:46- CWE-352 - Cross-Site Request Forgery (CSRF)
| URL | Tags |
|---|---|
| https://github.com/Thinkmill/keystatic/issues/1669 | issue-tracking |
| https://github.com/Thinkmill/keystatic/blob/b65d4… | technical-description |
| https://github.com/Thinkmill/keystatic/blob/b65d4… | technical-description |
| https://www.vulncheck.com/advisories/keystatic-th… | third-party-advisory |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-129945",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-16T17:46:19.671403Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T17:46:32.822Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:npm/%40keystatic/core",
"product": "Keystatic",
"repo": "https://github.com/Thinkmill/keystatic",
"vendor": "Thinkmill",
"versions": [
{
"lessThanOrEqual": "0.6.9",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Ikram-4"
}
],
"datePublic": "2026-11-16T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Keystatic through 0.6.9 contains a login cross-site request forgery vulnerability in the githubOauthCallback handler that allows unauthenticated remote attackers to sign victims in with the attacker\u0027s GitHub account by omitting state validation. Attackers can induce victims to visit the OAuth callback with an attacker-obtained authorization code, causing victim edits in the admin UI to be committed under the attacker\u0027s GitHub identity."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-16T15:06:12.002Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"tags": [
"issue-tracking"
],
"url": "https://github.com/Thinkmill/keystatic/issues/1669"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/Thinkmill/keystatic/blob/b65d4a55501dc3b7bb268dc925d8538a8a9f8e95/packages/keystatic/src/api/generic.ts#L199-L256"
},
{
"tags": [
"technical-description"
],
"url": "https://github.com/Thinkmill/keystatic/blob/b65d4a55501dc3b7bb268dc925d8538a8a9f8e95/packages/keystatic/src/api/generic.ts#L363-L398"
},
{
"name": "VulnCheck Advisory: Keystatic through 0.6.9 GitHub OAuth Login CSRF via Missing State Validation",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/keystatic-through-0.6.9-github-oauth-login-csrf-via-missing-state-validation"
}
],
"title": "Keystatic through 0.6.9 GitHub OAuth Login CSRF via Missing State Validation",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2026-129945",
"datePublished": "2026-11-16T15:06:12.002Z",
"dateReserved": "2026-11-16T14:43:32.492Z",
"dateUpdated": "2026-11-16T17:46:32.822Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Mitigation MIT-4
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
- For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
- Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
Mitigation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Mitigation
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
Mitigation
Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
Mitigation
- Use the "double-submitted cookie" method as described by Felten and Zeller:
- When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
- Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
- This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
Mitigation
Do not use the GET method for any request that triggers a state change.
Mitigation
Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
CAPEC-111: JSON Hijacking (aka JavaScript Hijacking)
An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website.
CAPEC-462: Cross-Domain Search Timing
An attacker initiates cross domain HTTP / GET requests and times the server responses. The timing of these responses may leak important information on what is happening on the server. Browser's same origin policy prevents the attacker from directly reading the server responses (in the absence of any other weaknesses), but does not prevent the attacker from timing the responses to requests that the attacker issued cross domain.
CAPEC-467: Cross Site Identification
An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the "remember me" feature to keep their session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing).
CAPEC-62: Cross Site Request Forgery
An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.