Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 03:05 UTC

Critical in the last 24 hours

1603 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

151-75% vs 7-day avg of 598

2 critical, 41 high, 61 medium, 27 low

Expand	Severity	Score	Advisory	Title	Source	Flags	Published
	High	7.1	CVE-2026-114659	Grav Flex Objects plugin 1.4.0 before 1.4.17 contains an authorization bypass because its generic /api/v1/flex-objects/pages API routes check only directory-level admin.pages... getgrav, Gravgetgrav grav-plugin-flex-objects, Grav Flex Objects plugin, Grav API plugin	NVD		Oct 22 02:16 UTC
CVE-2026-114659Grav Flex Objects plugin 1.4.0 before 1.4.17 contains an authorization bypass because its generic /api/v1/flex-objects/pages API routes check only directory-level admin.pages... Executive summary A flaw in the Flex Objects plugin for the Grav content platform lets signed-in, non-super accounts with API access read, change, or delete pages they should be blocked from. The advisory rates it Moderate and says the fix is to update Flex Objects to 1.4.17 or, if that is not possible right away, to remove the affected admin permissions or API access from non-super accounts. Technical summary This is an authorization bypass (CWE-863, with CWE-424 alternate path) in the generic /api/v1/flex-objects/pages routes, which check only directory-level admin.pages permissions and skip the per-page api.pages.read and api.pages.write checks and page permissions rules that the Pages API enforces. The attacker needs an authenticated account with api.access plus admin.pages or admin.configuration.pages, and the advisory says it is not a super user account. Affected versions are Flex Objects >= 1.4.0, < 1.4.17 (1.4.0 through 1.4.16), with the fix in 1.4.17. The advisory states that the pages directory is enabled by default and that sites using API plugin 1.0.16 or later are affected when relying on page-level permissions rules. Workarounds are stated: remove admin.pages and admin.configuration.pages from non-super accounts and groups, or remove api.access from accounts that do not need it. The advisory does not state a CVE ID (it says 'No known CVE'), a CVSS score, whether the issue is exploited in the wild, or specific detection guidance. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/getgrav/grav/security/adviso…/GHSA-2pvc-r9gj-mcpf Impact if exploited ConfidentialityHigh IntegrityNone AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Attack requirements None Privileges required Low User interaction None CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/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 Affects getgrav Grav getgrav grav-plugin-flex-objects Grav Flex Objects plugin Grav API plugin NIST National Vulnerability DatabasePublished Oct 22, 2026 02:16 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee