CWE-862
Allowed-with-ReviewMissing Authorization
Abstraction: Class · Status: Incomplete
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
14609 vulnerabilities reference this CWE, most recent first.
GHSA-WV5F-24HF-9846
Vulnerability from github – Published: 2025-01-14 03:31 – Updated: 2025-01-14 03:31Due to a missing authorization check on service endpoints in the SAP NetWeaver Application Server Java, an attacker with standard user role can create JCo connection entries, which are used for remote function calls from or to the application server. This could lead to low impact on confidentiality, integrity, and availability of the application.
{
"affected": [],
"aliases": [
"CVE-2025-0067"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-14T01:15:16Z",
"severity": "MODERATE"
},
"details": "Due to a missing authorization check on service endpoints in the SAP NetWeaver Application Server Java, an attacker with standard user role can create JCo connection entries, which are used for remote function calls from or to the application server. This could lead to low impact on confidentiality, integrity, and availability of the application.",
"id": "GHSA-wv5f-24hf-9846",
"modified": "2025-01-14T03:31:42Z",
"published": "2025-01-14T03:31:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0067"
},
{
"type": "WEB",
"url": "https://me.sap.com/notes/3540108"
},
{
"type": "WEB",
"url": "https://url.sap/sapsecuritypatchday"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-WV8M-CHCW-6W78
Vulnerability from github – Published: 2021-12-16 00:00 – Updated: 2021-12-22 00:01A missing authorization vulnerability in the web management interface of FatPipe WARP, IPVPN, and MPVPN software prior to versions 10.1.2r60p91 and 10.2.2r42 allows a remote attacker to access at least the URL "/fpui/jsp/index.jsp" leading to unknown impact, presumably some violation of confidentiality. Older versions of FatPipe software may also be vulnerable. The FatPipe advisory identifier for this vulnerability is FPSA004.
{
"affected": [],
"aliases": [
"CVE-2021-27858"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-15T20:15:00Z",
"severity": "MODERATE"
},
"details": "A missing authorization vulnerability in the web management interface of FatPipe WARP, IPVPN, and MPVPN software prior to versions 10.1.2r60p91 and 10.2.2r42 allows a remote attacker to access at least the URL \"/fpui/jsp/index.jsp\" leading to unknown impact, presumably some violation of confidentiality. Older versions of FatPipe software may also be vulnerable. The FatPipe advisory identifier for this vulnerability is FPSA004.",
"id": "GHSA-wv8m-chcw-6w78",
"modified": "2021-12-22T00:01:44Z",
"published": "2021-12-16T00:00:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-27858"
},
{
"type": "WEB",
"url": "https://www.fatpipeinc.com/support/cve-list.php"
},
{
"type": "WEB",
"url": "https://www.zeroscience.mk/codes/fatpipe_auth.txt"
},
{
"type": "WEB",
"url": "https://www.zeroscience.mk/en/vulnerabilities/ZSL-2021-5682.php"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-WVC4-6XQP-9V2F
Vulnerability from github – Published: 2026-01-23 15:31 – Updated: 2026-01-23 21:30Missing Authorization vulnerability in pencilwp X Addons for Elementor x-addons-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects X Addons for Elementor: from n/a through <= 1.0.23.
{
"affected": [],
"aliases": [
"CVE-2026-24605"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-23T15:16:19Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in pencilwp X Addons for Elementor x-addons-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects X Addons for Elementor: from n/a through \u003c= 1.0.23.",
"id": "GHSA-wvc4-6xqp-9v2f",
"modified": "2026-01-23T21:30:43Z",
"published": "2026-01-23T15:31:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24605"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/x-addons-elementor/vulnerability/wordpress-x-addons-for-elementor-plugin-1-0-23-broken-access-control-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WVF6-CQWC-CF6X
Vulnerability from github – Published: 2022-05-24 17:29 – Updated: 2023-05-22 21:30A vulnerability in the Cisco IOS XE ROM Monitor (ROMMON) Software for Cisco 4000 Series Integrated Services Routers, Cisco ASR 920 Series Aggregation Services Routers, Cisco ASR 1000 Series Aggregation Services Routers, and Cisco cBR-8 Converged Broadband Routers could allow an unauthenticated, physical attacker to break the chain of trust and load a compromised software image on an affected device. The vulnerability is due to the presence of a debugging configuration option in the affected software. An attacker could exploit this vulnerability by connecting to an affected device through the console, forcing the device into ROMMON mode, and writing a malicious pattern using that specific option on the device. A successful exploit could allow the attacker to break the chain of trust and load a compromised software image on the affected device. A compromised software image is any software image that has not been digitally signed by Cisco.
{
"affected": [],
"aliases": [
"CVE-2020-3524"
],
"database_specific": {
"cwe_ids": [
"CWE-284",
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-09-24T18:15:00Z",
"severity": "MODERATE"
},
"details": "A vulnerability in the Cisco IOS XE ROM Monitor (ROMMON) Software for Cisco 4000 Series Integrated Services Routers, Cisco ASR 920 Series Aggregation Services Routers, Cisco ASR 1000 Series Aggregation Services Routers, and Cisco cBR-8 Converged Broadband Routers could allow an unauthenticated, physical attacker to break the chain of trust and load a compromised software image on an affected device. The vulnerability is due to the presence of a debugging configuration option in the affected software. An attacker could exploit this vulnerability by connecting to an affected device through the console, forcing the device into ROMMON mode, and writing a malicious pattern using that specific option on the device. A successful exploit could allow the attacker to break the chain of trust and load a compromised software image on the affected device. A compromised software image is any software image that has not been digitally signed by Cisco.",
"id": "GHSA-wvf6-cqwc-cf6x",
"modified": "2023-05-22T21:30:18Z",
"published": "2022-05-24T17:29:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-3524"
},
{
"type": "WEB",
"url": "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-rommon-secboot-7JgVLVYC"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-WVG9-VC45-V9RF
Vulnerability from github – Published: 2025-12-03 15:30 – Updated: 2025-12-03 15:30The Post SMTP plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.6.1. This is due to the plugin not properly verifying that a user is authorized to update OAuth tokens on the 'handle_gmail_oauth_redirect' function. This makes it possible for authenticated attackers, with subscriber level access and above, to inject invalid or attacker-controlled OAuth credentials.
{
"affected": [],
"aliases": [
"CVE-2025-12887"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-03T13:16:01Z",
"severity": "MODERATE"
},
"details": "The Post SMTP plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.6.1. This is due to the plugin not properly verifying that a user is authorized to update OAuth tokens on the \u0027handle_gmail_oauth_redirect\u0027 function. This makes it possible for authenticated attackers, with subscriber level access and above, to inject invalid or attacker-controlled OAuth credentials.",
"id": "GHSA-wvg9-vc45-v9rf",
"modified": "2025-12-03T15:30:28Z",
"published": "2025-12-03T15:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-12887"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3402203"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/5bd9f312-99e1-4dc2-855d-90339c2e24da?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-WVHV-JQPM-79VJ
Vulnerability from github – Published: 2022-10-04 00:00 – Updated: 2022-10-05 00:00The Frontend File Manager Plugin WordPress plugin before 21.3 allows any unauthenticated user to rename uploaded files from users. Furthermore, due to the lack of validation in the destination filename, this could allow allow them to change the content of arbitrary files on the web server
{
"affected": [],
"aliases": [
"CVE-2022-3124"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-10-03T14:15:00Z",
"severity": "MODERATE"
},
"details": "The Frontend File Manager Plugin WordPress plugin before 21.3 allows any unauthenticated user to rename uploaded files from users. Furthermore, due to the lack of validation in the destination filename, this could allow allow them to change the content of arbitrary files on the web server",
"id": "GHSA-wvhv-jqpm-79vj",
"modified": "2022-10-05T00:00:37Z",
"published": "2022-10-04T00:00:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-3124"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/00f76765-95af-4dbc-8c37-f1b15a0e8608"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WVHV-QCQF-F3CX
Vulnerability from github – Published: 2026-04-10 20:00 – Updated: 2026-04-15 21:06Summary
goshs enforces the documented per-folder .goshs ACL/basic-auth mechanism for directory listings and file reads, but it does not enforce the same authorization checks for state-changing routes. An unauthenticated attacker can upload files with PUT, upload files with multipart POST /upload, create directories with ?mkdir, and delete files with ?delete inside a .goshs-protected directory. By deleting the .goshs file itself, the attacker can remove the folder's auth policy and then access previously protected content without credentials. This results in a critical authorization bypass affecting confidentiality, integrity, and availability.
Details
The project README explicitly documents file-based ACLs as a security feature:
README.md:59- "You can place a .goshs in any folder to apply custom ACLs"README.md:61- "You can apply custom basic auth per folder"
The read/list path correctly enforces .goshs:
httpserver/filebased.go:10-49loads.goshshttpserver/handler.go:68-91callsfindSpecialFile()for directorieshttpserver/handler.go:94-101callsfindSpecialFile()for fileshttpserver/handler.go:285-305applies custom authhttpserver/handler.go:545-565enforces folder auth during directory renderinghttpserver/handler.go:590-630enforces file auth and blocked entries during file serving
However, the state-changing routes bypass this logic entirely:
httpserver/server.go:94-100routes multipartPOST /.../uploaddirectly toupload()httpserver/server.go:105-109routesPUTdirectly toput()httpserver/handler.go:119-123dispatches?mkdirdirectly tohandleMkdir()httpserver/handler.go:181-187dispatches?deletedirectly todeleteFile()httpserver/updown.go:18-60writes files forPUTwithout checking.goshshttpserver/updown.go:63-165writes files for multipart upload without checking.goshshttpserver/handler.go:679-698deletes files withos.RemoveAll()without checking.goshshttpserver/handler.go:901-937creates directories withos.MkdirAll()without checking.goshs
This is not a path traversal issue. The path remains inside the configured root after sanitization. The vulnerability is that authorization is applied inconsistently: reads are protected, but writes and deletes are not. Because .goshs itself can be deleted through the unauthenticated delete route, the attacker can escalate the impact from unauthorized modification to full removal of the folder's auth barrier.
PoC
Environment used for verification:
- Repository/module:
github.com/patrickhener/goshs - Verified vulnerable tag:
v2.0.0-beta.3 - Also present in the
v1.1.4line based on code inspection - Local host:
127.0.0.1:18091
Build and setup:
cd '/Users/r1zzg0d/Documents/CVE hunting/targets/goshs_beta3'
go build -o /tmp/goshs_acl_verify/goshs ./
rm -rf /tmp/goshs_acl_verify/root
mkdir -p /tmp/goshs_acl_verify/root/protected
cp integration/keepFiles/goshsACLAuth /tmp/goshs_acl_verify/root/protected/.goshs
printf 'top secret\n' > /tmp/goshs_acl_verify/root/protected/secret.txt
/tmp/goshs_acl_verify/goshs -d /tmp/goshs_acl_verify/root -p 18091
In a second terminal:
# The protected folder initially requires auth
curl -s -o /dev/null -w '%{http_code}\n' 'http://127.0.0.1:18091/protected/'
# Unauthenticated write into the protected folder succeeds
curl -s -o /dev/null -w '%{http_code}\n' -X PUT \
--data-binary 'injected via PUT' \
'http://127.0.0.1:18091/protected/put-created.txt'
# Unauthenticated deletion of the ACL file succeeds
curl -s -o /dev/null -w '%{http_code}\n' \
'http://127.0.0.1:18091/protected/.goshs?delete'
# The previously protected file is now publicly accessible
curl -s -o /dev/null -w '%{http_code}\n' \
'http://127.0.0.1:18091/protected/secret.txt'
curl -s 'http://127.0.0.1:18091/protected/secret.txt'
Expected results:
401
200
200
200
top secret
Note: if using zsh, the URL containing ?delete must be quoted, or the shell will treat ? as a wildcard and the request will not be sent.
PoC Video for reference:
https://github.com/user-attachments/assets/deb9106e-6dfa-47c0-95c1-993c2cbc9ee7
Impact
This is an authorization bypass affecting deployments that rely on .goshs for per-folder protection. A remote unauthenticated attacker can:
- create or overwrite files inside a folder that should require authentication
- create directories inside the protected folder
- delete arbitrary files reachable through the vulnerable route inside that protected folder
- delete the
.goshspolicy file itself - read previously protected files once the policy file has been removed
In practice, this breaks the security boundary promised by the file-based ACL feature and can expose sensitive files while also allowing unauthorized modification or destruction of protected content.
Remediation
- Enforce
.goshsauthorization checks for all state-changing operations, not just read/list flows. BeforePUT, multipart upload, delete, and mkdir, resolve the effective folder ACL and deny the request unless the caller satisfiesacl.Auth. - Protect
.goshsas a special file in mutation handlers. The application already prevents serving.goshs; it should also reject deletion, overwrite, or replacement of.goshsthrough HTTP routes unless the request is properly authorized. - Add regression tests covering protected folders for every mutation path. The test suite should verify that
PUT,POST /upload,?delete, and?mkdirall fail without valid credentials when a.goshsfile is present.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/patrickhener/goshs"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "1.1.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-40189"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-10T20:00:32Z",
"nvd_published_at": "2026-04-10T20:16:23Z",
"severity": "CRITICAL"
},
"details": "### Summary\ngoshs enforces the documented per-folder `.goshs` ACL/basic-auth mechanism for directory listings and file reads, but it does not enforce the same authorization checks for state-changing routes. An unauthenticated attacker can upload files with `PUT`, upload files with multipart `POST /upload`, create directories with `?mkdir`, and delete files with `?delete` inside a `.goshs`-protected directory. By deleting the `.goshs` file itself, the attacker can remove the folder\u0027s auth policy and then access previously protected content without credentials. This results in a critical authorization bypass affecting confidentiality, integrity, and availability.\n\n### Details\nThe project README explicitly documents file-based ACLs as a security feature:\n\n- `README.md:59` - \"You can place a .goshs in any folder to apply custom ACLs\"\n- `README.md:61` - \"You can apply custom basic auth per folder\"\n\nThe read/list path correctly enforces `.goshs`:\n\n- `httpserver/filebased.go:10-49` loads `.goshs`\n- `httpserver/handler.go:68-91` calls `findSpecialFile()` for directories\n- `httpserver/handler.go:94-101` calls `findSpecialFile()` for files\n- `httpserver/handler.go:285-305` applies custom auth\n- `httpserver/handler.go:545-565` enforces folder auth during directory rendering\n- `httpserver/handler.go:590-630` enforces file auth and blocked entries during file serving\n\nHowever, the state-changing routes bypass this logic entirely:\n\n- `httpserver/server.go:94-100` routes multipart `POST /.../upload` directly to `upload()`\n- `httpserver/server.go:105-109` routes `PUT` directly to `put()`\n- `httpserver/handler.go:119-123` dispatches `?mkdir` directly to `handleMkdir()`\n- `httpserver/handler.go:181-187` dispatches `?delete` directly to `deleteFile()`\n- `httpserver/updown.go:18-60` writes files for `PUT` without checking `.goshs`\n- `httpserver/updown.go:63-165` writes files for multipart upload without checking `.goshs`\n- `httpserver/handler.go:679-698` deletes files with `os.RemoveAll()` without checking `.goshs`\n- `httpserver/handler.go:901-937` creates directories with `os.MkdirAll()` without checking `.goshs`\n\nThis is not a path traversal issue. The path remains inside the configured root after sanitization. The vulnerability is that authorization is applied inconsistently: reads are protected, but writes and deletes are not. Because `.goshs` itself can be deleted through the unauthenticated delete route, the attacker can escalate the impact from unauthorized modification to full removal of the folder\u0027s auth barrier.\n\n### PoC\nEnvironment used for verification:\n\n- Repository/module: `github.com/patrickhener/goshs`\n- Verified vulnerable tag: `v2.0.0-beta.3`\n- Also present in the `v1.1.4` line based on code inspection\n- Local host: `127.0.0.1:18091`\n\nBuild and setup:\n\n```bash\ncd \u0027/Users/r1zzg0d/Documents/CVE hunting/targets/goshs_beta3\u0027\ngo build -o /tmp/goshs_acl_verify/goshs ./\n\nrm -rf /tmp/goshs_acl_verify/root\nmkdir -p /tmp/goshs_acl_verify/root/protected\ncp integration/keepFiles/goshsACLAuth /tmp/goshs_acl_verify/root/protected/.goshs\nprintf \u0027top secret\\n\u0027 \u003e /tmp/goshs_acl_verify/root/protected/secret.txt\n\n/tmp/goshs_acl_verify/goshs -d /tmp/goshs_acl_verify/root -p 18091\n```\n\nIn a second terminal:\n\n```bash\n# The protected folder initially requires auth\ncurl -s -o /dev/null -w \u0027%{http_code}\\n\u0027 \u0027http://127.0.0.1:18091/protected/\u0027\n\n# Unauthenticated write into the protected folder succeeds\ncurl -s -o /dev/null -w \u0027%{http_code}\\n\u0027 -X PUT \\\n --data-binary \u0027injected via PUT\u0027 \\\n \u0027http://127.0.0.1:18091/protected/put-created.txt\u0027\n\n# Unauthenticated deletion of the ACL file succeeds\ncurl -s -o /dev/null -w \u0027%{http_code}\\n\u0027 \\\n \u0027http://127.0.0.1:18091/protected/.goshs?delete\u0027\n\n# The previously protected file is now publicly accessible\ncurl -s -o /dev/null -w \u0027%{http_code}\\n\u0027 \\\n \u0027http://127.0.0.1:18091/protected/secret.txt\u0027\ncurl -s \u0027http://127.0.0.1:18091/protected/secret.txt\u0027\n```\n\nExpected results:\n\n```text\n401\n200\n200\n200\ntop secret\n```\n\u003cimg width=\"1280\" height=\"657\" alt=\"goshs_poc1\" src=\"https://github.com/user-attachments/assets/37576067-fa90-44f6-8fe5-dcb7c96b9704\" /\u003e\n\n\nNote: if using `zsh`, the URL containing `?delete` must be quoted, or the shell will treat `?` as a wildcard and the request will not be sent.\n\nPoC Video for reference:\n\nhttps://github.com/user-attachments/assets/deb9106e-6dfa-47c0-95c1-993c2cbc9ee7\n\n\n### Impact\nThis is an authorization bypass affecting deployments that rely on `.goshs` for per-folder protection. A remote unauthenticated attacker can:\n\n- create or overwrite files inside a folder that should require authentication\n- create directories inside the protected folder\n- delete arbitrary files reachable through the vulnerable route inside that protected folder\n- delete the `.goshs` policy file itself\n- read previously protected files once the policy file has been removed\n\nIn practice, this breaks the security boundary promised by the file-based ACL feature and can expose sensitive files while also allowing unauthorized modification or destruction of protected content.\n\n### Remediation\n1. Enforce `.goshs` authorization checks for all state-changing operations, not just read/list flows. Before `PUT`, multipart upload, delete, and mkdir, resolve the effective folder ACL and deny the request unless the caller satisfies `acl.Auth`.\n2. Protect `.goshs` as a special file in mutation handlers. The application already prevents serving `.goshs`; it should also reject deletion, overwrite, or replacement of `.goshs` through HTTP routes unless the request is properly authorized.\n3. Add regression tests covering protected folders for every mutation path. The test suite should verify that `PUT`, `POST /upload`, `?delete`, and `?mkdir` all fail without valid credentials when a `.goshs` file is present.",
"id": "GHSA-wvhv-qcqf-f3cx",
"modified": "2026-04-15T21:06:24Z",
"published": "2026-04-10T20:00:32Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/patrickhener/goshs/security/advisories/GHSA-wvhv-qcqf-f3cx"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40189"
},
{
"type": "WEB",
"url": "https://github.com/patrickhener/goshs/commit/f212c4f4a126556bab008f79758e21a839ef2c0f"
},
{
"type": "PACKAGE",
"url": "https://github.com/patrickhener/goshs"
},
{
"type": "WEB",
"url": "https://github.com/patrickhener/goshs/releases/tag/v2.0.0-beta.4"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "goshs has a file-based ACL authorization bypass in goshs state-changing routes"
}
GHSA-WVM9-MQ8W-WRM8
Vulnerability from github – Published: 2023-10-20 09:30 – Updated: 2024-04-04 08:50The wpDiscuz plugin for WordPress is vulnerable to unauthorized modification of data due to a missing authorization check on the voteOnComment function in versions up to, and including, 7.6.3. This makes it possible for unauthenticated attackers to increase or decrease the rating of a comment.
{
"affected": [],
"aliases": [
"CVE-2023-3869"
],
"database_specific": {
"cwe_ids": [
"CWE-639",
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-10-20T08:15:12Z",
"severity": "MODERATE"
},
"details": "The wpDiscuz plugin for WordPress is vulnerable to unauthorized modification of data due to a missing authorization check on the voteOnComment function in versions up to, and including, 7.6.3. This makes it possible for unauthenticated attackers to increase or decrease the rating of a comment.",
"id": "GHSA-wvm9-mq8w-wrm8",
"modified": "2024-04-04T08:50:40Z",
"published": "2023-10-20T09:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3869"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/wpdiscuz/trunk/utils/class.WpdiscuzHelperAjax.php#L681"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/b30ac1b0-eae2-4194-bf8e-ae73b4236965?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WVQG-M8F5-6FPX
Vulnerability from github – Published: 2024-10-21 12:30 – Updated: 2026-04-01 18:32Missing Authorization vulnerability in Colorlib Simple Custom Post Order allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Simple Custom Post Order: from n/a through 2.5.7.
{
"affected": [],
"aliases": [
"CVE-2024-49321"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-10-21T12:15:08Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in Colorlib Simple Custom Post Order allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Simple Custom Post Order: from n/a through 2.5.7.",
"id": "GHSA-wvqg-m8f5-6fpx",
"modified": "2026-04-01T18:32:09Z",
"published": "2024-10-21T12:30:56Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49321"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/simple-custom-post-order/vulnerability/wordpress-simple-custom-post-order-plugin-2-5-7-broken-access-control-vulnerability?_s_id=cve"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/simple-custom-post-order/wordpress-simple-custom-post-order-plugin-2-5-7-broken-access-control-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-WVR2-CC2W-G93Q
Vulnerability from github – Published: 2023-05-09 03:30 – Updated: 2024-04-04 03:54In dialer service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.
{
"affected": [],
"aliases": [
"CVE-2022-48379"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-05-09T02:15:11Z",
"severity": "MODERATE"
},
"details": "In dialer service, there is a possible missing permission check. This could lead to local denial of service with no additional execution privileges.",
"id": "GHSA-wvr2-cc2w-g93q",
"modified": "2024-04-04T03:54:44Z",
"published": "2023-05-09T03:30:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48379"
},
{
"type": "WEB",
"url": "https://www.unisoc.com/en_us/secy/announcementDetail/1654776866982133761"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
- Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Mitigation
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
Mitigation MIT-4.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.
- For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Mitigation
- For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
- One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
Mitigation
Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
CAPEC-665: Exploitation of Thunderbolt Protection Flaws
An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.