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.
20286 vulnerabilities reference this CWE, most recent first.
GHSA-VMVQ-FH49-9M4Q
Vulnerability from github – Published: 2025-01-02 15:31 – Updated: 2025-01-02 15:31Missing Authorization vulnerability in Galleryape Gallery Images Ape allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Gallery Images Ape: from n/a through 2.2.8.
{
"affected": [],
"aliases": [
"CVE-2022-41995"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-02T15:15:17Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in Galleryape Gallery Images Ape allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Gallery Images Ape: from n/a through 2.2.8.",
"id": "GHSA-vmvq-fh49-9m4q",
"modified": "2025-01-02T15:31:58Z",
"published": "2025-01-02T15:31:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-41995"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/gallery-images-ape/vulnerability/wordpress-gallery-images-ape-plugin-2-2-8-auth-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-VMWX-8PMG-4MRR
Vulnerability from github – Published: 2023-07-06 19:24 – Updated: 2024-04-04 05:34The WordPress Shortcodes Plugin — Shortcodes Ultimate WordPress plugin before 5.12.8 does not ensure that posts to be displayed via some shortcodes are already public and can be accessed by the user making the request, allowing any authenticated users such as subscriber to view draft, private or even password protected posts. It is also possible to leak the password of protected posts
{
"affected": [],
"aliases": [
"CVE-2023-0890"
],
"database_specific": {
"cwe_ids": [
"CWE-200",
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-03-20T16:15:00Z",
"severity": "MODERATE"
},
"details": "The WordPress Shortcodes Plugin \u2014 Shortcodes Ultimate WordPress plugin before 5.12.8 does not ensure that posts to be displayed via some shortcodes are already public and can be accessed by the user making the request, allowing any authenticated users such as subscriber to view draft, private or even password protected posts. It is also possible to leak the password of protected posts",
"id": "GHSA-vmwx-8pmg-4mrr",
"modified": "2024-04-04T05:34:51Z",
"published": "2023-07-06T19:24:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-0890"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/8a466f15-f112-4527-8b02-4544a8032671"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-VMWX-M75V-QVCH
Vulnerability from github – Published: 2026-07-08 20:24 – Updated: 2026-07-08 20:24Impact
The create and store endpoints of the Quick Creation Command feature did not enforce any authorization check. An authenticated Sharp user without create permission on a given entity could bypass the authorization layer and either retrieve the creation form or submit new records for that entity, as long as it had a Quick Creation Command handler configured.
Patches
Yes. The fix is included in version 9.22.3. Users should upgrade to that version or later.
Workarounds
Remove or disable Quick Creation Command handlers (quickCreationCommandHandler()) on any entity list where unauthorized access is a concern, until an upgrade is possible.
Resources
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "code16/sharp"
},
"ranges": [
{
"events": [
{
"introduced": "9.0.0"
},
{
"fixed": "9.22.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-53634"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-08T20:24:36Z",
"nvd_published_at": "2026-06-10T22:17:01Z",
"severity": "MODERATE"
},
"details": "### Impact\nThe create and store endpoints of the Quick Creation Command feature did not enforce any authorization check. An authenticated Sharp user without create permission on a given entity could bypass the authorization layer and either retrieve the creation form or submit new records for that entity, as long as it had a Quick Creation Command handler configured.\n\n### Patches\nYes. The fix is included in version 9.22.3. Users should upgrade to that version or later.\n\n### Workarounds\nRemove or disable Quick Creation Command handlers (quickCreationCommandHandler()) on any entity list where unauthorized access is a concern, until an upgrade is possible.\n\n### Resources\n[PR #729](https://github.com/code16/sharp/pull/729)",
"id": "GHSA-vmwx-m75v-qvch",
"modified": "2026-07-08T20:24:36Z",
"published": "2026-07-08T20:24:36Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/code16/sharp/security/advisories/GHSA-vmwx-m75v-qvch"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-53634"
},
{
"type": "WEB",
"url": "https://github.com/code16/sharp/pull/729"
},
{
"type": "WEB",
"url": "https://github.com/code16/sharp/commit/aa18a85fd8fef830988a336cad2278986729d21a"
},
{
"type": "PACKAGE",
"url": "https://github.com/code16/sharp"
},
{
"type": "WEB",
"url": "https://github.com/code16/sharp/releases/tag/v9.22.3"
}
],
"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"
}
],
"summary": "Sharp Missing Authorization Check in Quick Creation Command Endpoints"
}
GHSA-VMX5-XFWF-9F82
Vulnerability from github – Published: 2024-06-11 18:30 – Updated: 2024-06-11 18:30Missing Authorization vulnerability in Wpmet WP Fundraising Donation and Crowdfunding Platform.This issue affects WP Fundraising Donation and Crowdfunding Platform: from n/a through 1.6.4.
{
"affected": [],
"aliases": [
"CVE-2024-34758"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-06-11T17:16:00Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in Wpmet WP Fundraising Donation and Crowdfunding Platform.This issue affects WP Fundraising Donation and Crowdfunding Platform: from n/a through 1.6.4.",
"id": "GHSA-vmx5-xfwf-9f82",
"modified": "2024-06-11T18:30:50Z",
"published": "2024-06-11T18:30:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-34758"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/wp-fundraising-donation/wordpress-fundengine-donation-and-crowdfunding-platform-plugin-1-6-4-broken-access-control-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-VMX9-CF98-29XX
Vulnerability from github – Published: 2025-01-07 18:30 – Updated: 2026-04-28 21:35Missing Authorization vulnerability in DearHive Social Media Share Buttons | MashShare.This issue affects Social Media Share Buttons | MashShare: from n/a through 4.0.47.
{
"affected": [],
"aliases": [
"CVE-2025-22319"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-07T17:15:32Z",
"severity": "MODERATE"
},
"details": "Missing Authorization vulnerability in DearHive Social Media Share Buttons | MashShare.This issue affects Social Media Share Buttons | MashShare: from n/a through 4.0.47.",
"id": "GHSA-vmx9-cf98-29xx",
"modified": "2026-04-28T21:35:30Z",
"published": "2025-01-07T18:30:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22319"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/mashsharer/vulnerability/wordpress-mashshare-plugin-4-0-47-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-VMXH-77CW-65J7
Vulnerability from github – Published: 2026-10-20 18:19 – Updated: 2026-10-20 18:19Summary ApostropheCMS’s exist-in-locale API allows an authenticated low-privilege user to determine whether restricted documents exist in a specified locale and mode, including draft mode. The endpoint returns localized document identifiers without applying document-level view or edit authorization criteria.
The issue was reproduced against a real local ApostropheCMS application running the reviewed source code. The test used a synthetic guest account and synthetic restricted draft records.
Details
Exact vulnerable source path: packages/apostrophe/modules/@apostrophecms/i18n/index.js:503-529
Exact API route:POST /api/v1/@apostrophecms/i18n/exist-in-locale
The handler verifies only that the requester is authenticated:
if (!req.user) {
throw self.apos.error('notfound');
}
It then performs a direct database lookup using attacker-controlled document IDs, locale, and mode:
const found = await self.apos.doc.db.find({
aposLocale: `${locale}:${mode}`,
aposDocId: {
$in: ids.map(self.apos.doc.toAposDocId)
}
}).project({
_id: 1,
aposDocId: 1
}).toArray();
This query does not apply:
.permission('view') .permission('edit') apos.permission.criteria(req, 'view') object-level document authorization locale-specific authorization
The endpoint accepts multiple IDs, making bulk probing possible.
Proof of Concept
The local application was running at: http://127.0.0.1:3000 The test account had the low-privilege role: guest The local database contained synthetic records for the restricted document base ID:
wv2l4rbaplgzkg80zkne4aoz:en:draft
wv2l4rbaplgzkg80zkne4aoz:fr:draft
All credentials and cookies are intentionally redacted below.
POST /api/v1/@apostrophecms/i18n/exist-in-locale HTTP/1.1
Host: 127.0.0.1:3000
Cookie: <redacted-authenticated-guest-session>
Content-Type: application/json
Accept: application/json
{
"ids": [
"wv2l4rbaplgzkg80zkne4aoz:en:draft",
"ckzzzzzzzzzzzzzzzzzzzzzzz:en:draft"
],
"locale": "fr",
"mode": "draft"
}
Equivalent command
curl -i -sS -X POST \
'http://127.0.0.1:3000/api/v1/@apostrophecms/i18n/exist-in-locale' \
-b /path/to/redacted-guest-cookie-jar.txt \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
"ids": [
"wv2l4rbaplgzkg80zkne4aoz:en:draft",
"ckzzzzzzzzzzzzzzzzzzzzzzz:en:draft"
],
"locale": "fr",
"mode": "draft"
}'
Observed response
HTTP/1.1 200 OK
X-Powered-By: Express
Content-Type: application/json; charset=utf-8
{
"originalLocaleIds": [
"wv2l4rbaplgzkg80zkne4aoz:en:draft"
],
"newLocaleIds": [
"wv2l4rbaplgzkg80zkne4aoz:fr:draft"
],
"aposDocIds": [
"wv2l4rbaplgzkg80zkne4aoz"
]
}
The nonexistent ID was omitted from the response. This proves that the endpoint acts as an existence oracle.
Authorization control Using the same authenticated guest session and the localized document identifier returned above, the normal page API was requested:
GET /api/v1/@apostrophecms/page/wv2l4rbaplgzkg80zkne4aoz:fr:draft HTTP/1.1
Host: 127.0.0.1:3000
Cookie: <redacted-authenticated-guest-session>
Accept: application/json
Observed response:
HTTP/1.1 403 Forbidden
Content-Type: application/json; charset=utf-8
{
"name": "forbidden",
"data": {},
"message": "forbidden"
}
This demonstrates the authorization boundary clearly:
| Request | Result |
|---|---|
| Normal page API for the restricted draft | 403 Forbidden |
exist-in-locale for the same restricted draft |
200 OK with localized document ID |
exist-in-locale for a nonexistent ID |
200 OK with empty arrays |
Additional impact validation
The behavior was also tested across multiple locale and mode combinations:
| Query | Result |
|---|---|
locale=fr, mode=draft |
Returned wv2l4rbaplgzkg80zkne4aoz:fr:draft |
locale=fr, mode=published |
Returned empty arrays because no published fixture existed |
locale=de, mode=draft |
Returned empty arrays because no German fixture existed |
| Two IDs in one request | Existing ID returned; nonexistent ID omitted |
This confirms that the endpoint can be used to discover whether a document has a localized draft in a particular locale and to perform bulk enumeration.
Impact A low-privilege authenticated user can: Probe arbitrary known or guessed document base IDs. Determine whether restricted documents have localized versions. Determine whether unpublished draft versions exist. Identify which locales contain matching records. Obtain exact localized document identifiers. Submit multiple IDs in one request for bulk reconnaissance. The issue does not directly disclose the document body or grant write, publish, or delete privileges. During testing, no content was modified, published, deleted, or exposed beyond the identifier metadata.
Recommended remediation Before executing the database lookup, apply the same document-level authorization criteria used by the normal document API. The query should be restricted to documents the requester is authorized to view in the requested locale and mode. Draft queries should additionally require the appropriate draft-view permission for the specific document, not merely authentication or a global role check. The endpoint should also avoid returning localized document identifiers for records that fail the requester’s document-level permission criteria.
[1] ApostropheCMS i18n source — existInLocale handler, lines 503–529
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "apostrophe"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.33.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-113660"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-20T18:19:34Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "**Summary**\nApostropheCMS\u2019s exist-in-locale API allows an authenticated low-privilege user to determine whether restricted documents exist in a specified locale and mode, including draft mode. The endpoint returns localized document identifiers without applying document-level view or edit authorization criteria.\n\nThe issue was reproduced against a real local ApostropheCMS application running the reviewed source code. The test used a synthetic guest account and synthetic restricted draft records.\n\n**Details**\nExact vulnerable source path: ` packages/apostrophe/modules/@apostrophecms/i18n/index.js:503-529`\nExact API route:` POST /api/v1/@apostrophecms/i18n/exist-in-locale`\nThe handler verifies only that the requester is authenticated:\n\n```\nif (!req.user) {\n throw self.apos.error(\u0027notfound\u0027);\n}\n```\nIt then performs a direct database lookup using attacker-controlled document IDs, locale, and mode:\n\n```\nconst found = await self.apos.doc.db.find({\n aposLocale: `${locale}:${mode}`,\n aposDocId: {\n $in: ids.map(self.apos.doc.toAposDocId)\n }\n}).project({\n _id: 1,\n aposDocId: 1\n}).toArray();\n```\nThis query does not apply:\n\n.permission(\u0027view\u0027)\n.permission(\u0027edit\u0027)\napos.permission.criteria(req, \u0027view\u0027)\nobject-level document authorization\nlocale-specific authorization\n\nThe endpoint accepts multiple IDs, making bulk probing possible.\n\n**Proof of Concept**\n\nThe local application was running at: http://127.0.0.1:3000\nThe test account had the low-privilege role: guest\nThe local database contained synthetic records for the restricted document base ID:\n```\nwv2l4rbaplgzkg80zkne4aoz:en:draft\nwv2l4rbaplgzkg80zkne4aoz:fr:draft\n```\nAll credentials and cookies are intentionally redacted below.\n\n```\nPOST /api/v1/@apostrophecms/i18n/exist-in-locale HTTP/1.1\nHost: 127.0.0.1:3000\nCookie: \u003credacted-authenticated-guest-session\u003e\nContent-Type: application/json\nAccept: application/json\n\n{\n \"ids\": [\n \"wv2l4rbaplgzkg80zkne4aoz:en:draft\",\n \"ckzzzzzzzzzzzzzzzzzzzzzzz:en:draft\"\n ],\n \"locale\": \"fr\",\n \"mode\": \"draft\"\n}\n```\n**Equivalent command**\n```\ncurl -i -sS -X POST \\\n \u0027http://127.0.0.1:3000/api/v1/@apostrophecms/i18n/exist-in-locale\u0027 \\\n -b /path/to/redacted-guest-cookie-jar.txt \\\n -H \u0027Content-Type: application/json\u0027 \\\n -H \u0027Accept: application/json\u0027 \\\n --data-raw \u0027{\n \"ids\": [\n \"wv2l4rbaplgzkg80zkne4aoz:en:draft\",\n \"ckzzzzzzzzzzzzzzzzzzzzzzz:en:draft\"\n ],\n \"locale\": \"fr\",\n \"mode\": \"draft\"\n }\u0027\n```\n**Observed response**\n```\nHTTP/1.1 200 OK\nX-Powered-By: Express\nContent-Type: application/json; charset=utf-8\n```\n\n```\n{\n \"originalLocaleIds\": [\n \"wv2l4rbaplgzkg80zkne4aoz:en:draft\"\n ],\n \"newLocaleIds\": [\n \"wv2l4rbaplgzkg80zkne4aoz:fr:draft\"\n ],\n \"aposDocIds\": [\n \"wv2l4rbaplgzkg80zkne4aoz\"\n ]\n}\n```\nThe nonexistent ID was omitted from the response. This proves that the endpoint acts as an existence oracle.\n\n**Authorization control**\nUsing the same authenticated guest session and the localized document identifier returned above, the normal page API was requested:\n\n```\nGET /api/v1/@apostrophecms/page/wv2l4rbaplgzkg80zkne4aoz:fr:draft HTTP/1.1\nHost: 127.0.0.1:3000\nCookie: \u003credacted-authenticated-guest-session\u003e\nAccept: application/json\n\n```\n\n**Observed response:**\n```\nHTTP/1.1 403 Forbidden\nContent-Type: application/json; charset=utf-8\n```\n```\n{\n \"name\": \"forbidden\",\n \"data\": {},\n \"message\": \"forbidden\"\n}\n\n```\nThis demonstrates the authorization boundary clearly:\n\n| Request | Result |\n| ----------------------------------------------- | ----------------------------------- |\n| Normal page API for the restricted draft | `403 Forbidden` |\n| `exist-in-locale` for the same restricted draft | `200 OK` with localized document ID |\n| `exist-in-locale` for a nonexistent ID | `200 OK` with empty arrays |\n\n**Additional impact validation**\n\nThe behavior was also tested across multiple locale and mode combinations:\n\n| Query | Result |\n| ----------------------------- | ---------------------------------------------------------- |\n| `locale=fr`, `mode=draft` | Returned `wv2l4rbaplgzkg80zkne4aoz:fr:draft` |\n| `locale=fr`, `mode=published` | Returned empty arrays because no published fixture existed |\n| `locale=de`, `mode=draft` | Returned empty arrays because no German fixture existed |\n| Two IDs in one request | Existing ID returned; nonexistent ID omitted |\n\nThis confirms that the endpoint can be used to discover whether a document has a localized draft in a particular locale and to perform bulk enumeration.\n\nImpact\nA low-privilege authenticated user can:\nProbe arbitrary known or guessed document base IDs.\nDetermine whether restricted documents have localized versions.\nDetermine whether unpublished draft versions exist.\nIdentify which locales contain matching records.\nObtain exact localized document identifiers.\nSubmit multiple IDs in one request for bulk reconnaissance.\nThe issue does not directly disclose the document body or grant write, publish, or delete privileges. During testing, no content was modified, published, deleted, or exposed beyond the identifier metadata.\n\nRecommended remediation\nBefore executing the database lookup, apply the same document-level authorization criteria used by the normal document API. The query should be restricted to documents the requester is authorized to view in the requested locale and mode. Draft queries should additionally require the appropriate draft-view permission for the specific document, not merely authentication or a global role check.\nThe endpoint should also avoid returning localized document identifiers for records that fail the requester\u2019s document-level permission criteria.\n\n[[1] ApostropheCMS i18n source \u2014 existInLocale handler, lines 503\u2013529](https://github.com/apostrophecms/apostrophe/blob/61d137f31a0de15a8eb70b7e65032e0519fc6e61/packages/apostrophe/modules/@apostrophecms/i18n/index.js#L503-L529)\n\n[[2] Official ApostropheCMS i18n API documentation](https://apostrophecms.com/docs/reference/api/i18n.html)",
"id": "GHSA-vmxh-77cw-65j7",
"modified": "2026-10-20T18:19:34Z",
"published": "2026-10-20T18:19:34Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-vmxh-77cw-65j7"
},
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/commit/9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce"
},
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350"
},
{
"type": "PACKAGE",
"url": "https://github.com/apostrophecms/apostrophe"
},
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/releases/tag/apostrophe@4.33.0"
}
],
"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"
}
],
"summary": "ApostropheCMS: Authenticated Object-Level Authorization Bypass in exist-in-locale Reveals Restricted Localized Draft Identifiers"
}
GHSA-VP28-9CM6-HPWG
Vulnerability from github – Published: 2024-05-14 15:32 – Updated: 2024-05-14 15:32The SimpleShop plugin for WordPress is vulnerable to unauthorized disconnection from SimpleShop due to a missing capability check on the maybe_disconnect_simpleshop function in all versions up to, and including, 2.10.2. This makes it possible for unauthenticated attackers to disconnect the SimpleShop.
{
"affected": [],
"aliases": [
"CVE-2024-1229"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-05-14T14:45:42Z",
"severity": "MODERATE"
},
"details": "The SimpleShop plugin for WordPress is vulnerable to unauthorized disconnection from SimpleShop due to a missing capability check on the maybe_disconnect_simpleshop function in all versions up to, and including, 2.10.2. This makes it possible for unauthenticated attackers to disconnect the SimpleShop.",
"id": "GHSA-vp28-9cm6-hpwg",
"modified": "2024-05-14T15:32:51Z",
"published": "2024-05-14T15:32:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-1229"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/simpleshop-cz/trunk/src/Settings.php?rev=3019145#L341"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026old=3080151%40simpleshop-cz\u0026new=3080151%40simpleshop-cz\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/4dc39c47-3b99-4e43-b25d-a025f3d228b5?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-VP2H-6426-V5WH
Vulnerability from github – Published: 2026-10-21 03:32 – Updated: 2026-10-21 03:32ArcadeDB from 26.2.1 before 26.10.1 contains a missing authorization vulnerability in the Bolt protocol handler that allows authenticated users to enumerate all database names. Attackers with credentials for any single database can issue a SHOW DATABASES query over the Bolt port to reveal unauthorized database names, exposing tenant or project identifiers.
{
"affected": [],
"aliases": [
"CVE-2026-114057"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-21T01:17:28Z",
"severity": "MODERATE"
},
"details": "ArcadeDB from 26.2.1 before 26.10.1 contains a missing authorization vulnerability in the Bolt protocol handler that allows authenticated users to enumerate all database names. Attackers with credentials for any single database can issue a SHOW DATABASES query over the Bolt port to reveal unauthorized database names, exposing tenant or project identifiers.",
"id": "GHSA-vp2h-6426-v5wh",
"modified": "2026-10-21T03:32:16Z",
"published": "2026-10-21T03:32:16Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-7fcg-pg8x-wf7w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-114057"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/arcadedb-26.2.1-before-26.10.1-bolt-show-databases-information-disclosure"
}
],
"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"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-VP38-57W4-9685
Vulnerability from github – Published: 2023-03-10 21:30 – Updated: 2026-04-08 18:32The RapidLoad Power-Up for Autoptimize plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the clear_page_cache function in versions up to, and including, 1.7.1. This makes it possible for authenticated attackers with subscriber-level access to delete the plugin's cache.
{
"affected": [],
"aliases": [
"CVE-2023-1333"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-03-10T20:15:00Z",
"severity": "MODERATE"
},
"details": "The RapidLoad Power-Up for Autoptimize plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the clear_page_cache function in versions up to, and including, 1.7.1. This makes it possible for authenticated attackers with subscriber-level access to delete the plugin\u0027s cache.",
"id": "GHSA-vp38-57w4-9685",
"modified": "2026-04-08T18:32:03Z",
"published": "2023-03-10T21:30:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1333"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/2877726/unusedcss/trunk/includes/modules/unused-css/UnusedCSS_Admin.php?contextall=1\u0026old=2847136\u0026old_path=%2Funusedcss%2Ftrunk%2Fincludes%2Fmodules%2Funused-css%2FUnusedCSS_Admin.php"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/2cba74f7-7183-4297-8f04-4818c01358ef"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/2cba74f7-7183-4297-8f04-4818c01358ef?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:N",
"type": "CVSS_V3"
}
]
}
GHSA-VP4V-GJPC-C4X6
Vulnerability from github – Published: 2026-10-19 18:32 – Updated: 2026-10-19 18:32The ForgeRock client fails to correctly validate refresh tokens. This allows a refresh token to be treated as a valid access token, enabling its use for consuming protected resources. This bypasses the intended security control that requires valid client credentials in addition to a refresh token to obtain a new access token.
An attacker who obtains a stolen or exposed refresh token can leverage this vulnerability to directly access protected resources. This is possible because the standard security flow requiring client credentials to exchange a refresh token for an access token is circumvented.
{
"affected": [],
"aliases": [
"CVE-2025-7043"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-19T17:16:59Z",
"severity": "MODERATE"
},
"details": "The ForgeRock client fails to correctly validate refresh tokens. This allows a refresh token to be treated as a valid access token, enabling its use for consuming protected resources. This bypasses the intended security control that requires valid client credentials in addition to a refresh token to obtain a new access token.\n\nAn attacker who obtains a stolen or exposed refresh token can leverage this vulnerability to directly access protected resources. This is possible because the standard security flow requiring client credentials to exchange a refresh token for an access token is circumvented.",
"id": "GHSA-vp4v-gjpc-c4x6",
"modified": "2026-10-19T18:32:13Z",
"published": "2026-10-19T18:32:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-7043"
},
{
"type": "WEB",
"url": "https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4337"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N",
"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.