{"items":[{"id":"NVI-00003687","kind":"vulnerability","title":"Craft CMS: Entries Authorship Spoofing via Mass Assignment","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-2xfc-g69j-x2mp","CVE-2026-28781"],"plain_summary":"OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.9.0-beta.1 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.17.0-beta.1 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0bfb5fc44a32a0ff45fd11ec65adca63"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T10:29:01.963Z","value":"6.5 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-8b1d11cfafee70288f645bac92f8d512"},{"kind":"CVSS","as_of":"2026-06-17T10:29:01.963Z","value":"7.1 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-8b1d11cfafee70288f645bac92f8d512"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.388%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32893. Missing scores are unknown.","source_id":"sr-0bfb5fc44a32a0ff45fd11ec65adca63"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-47747ad4a55a11dadd6765ba45033175","url":"https://github.com/advisories/GHSA-2xfc-g69j-x2mp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2xfc-g69j-x2mp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.646Z"},{"id":"sr-8b1d11cfafee70288f645bac92f8d512","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-28781","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-28781","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:56.268Z"},{"id":"sr-0bfb5fc44a32a0ff45fd11ec65adca63","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-28781","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.271Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Description\nThe entry creation process allows for **Mass Assignment** of the `authorId` attribute. A user with \"Create Entries\" permission can inject the `authorIds[]` (or `authorId`) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others.\n\nNormally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively \"spoofs\" the authorship.\n\n## Proof of Concept\n### Prerequisites\n- A user account with \"Create Entries\" permission for a section.\n- Victim's account ID (e.g., `1` for the default Admin).\n\n### Steps to Reproduce\n1. Log in as the attacker\n1. Navigate to the \"Entries\" section and click \"New Entry\"\n1. Fill in the required fields\n1. Enable a proxy tool (e.g., Burp Suite) to intercept requests\n1. Click \"Save\" & Intercept the request\n1. In the request body, add a new parameter to the body params: `&authorIds[]=`\n1. Forward the request\n1. Log in as an admin / as with the victim account\n1. Go to entries & Observe the newly created entry is","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.9.0-beta.1"]},{"certainty":"source_listed","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Description\nThe entry creation process allows for **Mass Assignment** of the `authorId` attribute. A user with \"Create Entries\" permission can inject the `authorIds[]` (or `authorId`) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others.\n\nNormally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively \"spoofs\" the authorship.\n\n## Proof of Concept\n### Prerequisites\n- A user account with \"Create Entries\" permission for a section.\n- Victim's account ID (e.g., `1` for the default Admin).\n\n### Steps to Reproduce\n1. Log in as the attacker\n1. Navigate to the \"Entries\" section and click \"New Entry\"\n1. Fill in the required fields\n1. Enable a proxy tool (e.g., Burp Suite) to intercept requests\n1. Click \"Save\" & Intercept the request\n1. In the request body, add a new parameter to the body params: `&authorIds[]=`\n1. Forward the request\n1. Log in as an admin / as with the victim account\n1. Go to entries & Observe the newly created entry is","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.17.0-beta.1"]}],"null_published_at":"2026-11-03T17:49:21.365Z","source_updated_at":"2026-03-04T18:48:54.065Z","source_disclosed_at":"2026-03-03T21:00:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:49.646Z"},{"id":"NVI-00003687","kind":"vulnerability","title":"Craft CMS: Entries Authorship Spoofing via Mass Assignment","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2xfc-g69j-x2mp","CVE-2026-28781"],"plain_summary":"OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.9.0-beta.1 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.17.0-beta.1 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0bfb5fc44a32a0ff45fd11ec65adca63"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.388%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32893. Missing scores are unknown.","source_id":"sr-0bfb5fc44a32a0ff45fd11ec65adca63"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-47747ad4a55a11dadd6765ba45033175","url":"https://github.com/advisories/GHSA-2xfc-g69j-x2mp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2xfc-g69j-x2mp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.646Z"},{"id":"sr-0bfb5fc44a32a0ff45fd11ec65adca63","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-28781","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.271Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Description\nThe entry creation process allows for **Mass Assignment** of the `authorId` attribute. A user with \"Create Entries\" permission can inject the `authorIds[]` (or `authorId`) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others.\n\nNormally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively \"spoofs\" the authorship.\n\n## Proof of Concept\n### Prerequisites\n- A user account with \"Create Entries\" permission for a section.\n- Victim's account ID (e.g., `1` for the default Admin).\n\n### Steps to Reproduce\n1. Log in as the attacker\n1. Navigate to the \"Entries\" section and click \"New Entry\"\n1. Fill in the required fields\n1. Enable a proxy tool (e.g., Burp Suite) to intercept requests\n1. Click \"Save\" & Intercept the request\n1. In the request body, add a new parameter to the body params: `&authorIds[]=`\n1. Forward the request\n1. Log in as an admin / as with the victim account\n1. Go to entries & Observe the newly created entry is","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.9.0-beta.1"]},{"certainty":"source_listed","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Description\nThe entry creation process allows for **Mass Assignment** of the `authorId` attribute. A user with \"Create Entries\" permission can inject the `authorIds[]` (or `authorId`) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others.\n\nNormally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively \"spoofs\" the authorship.\n\n## Proof of Concept\n### Prerequisites\n- A user account with \"Create Entries\" permission for a section.\n- Victim's account ID (e.g., `1` for the default Admin).\n\n### Steps to Reproduce\n1. Log in as the attacker\n1. Navigate to the \"Entries\" section and click \"New Entry\"\n1. Fill in the required fields\n1. Enable a proxy tool (e.g., Burp Suite) to intercept requests\n1. Click \"Save\" & Intercept the request\n1. In the request body, add a new parameter to the body params: `&authorIds[]=`\n1. Forward the request\n1. Log in as an admin / as with the victim account\n1. Go to entries & Observe the newly created entry is","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.17.0-beta.1"]}],"null_published_at":"2026-11-02T20:21:07.849Z","source_updated_at":"2026-03-04T18:48:54.065Z","source_disclosed_at":"2026-03-03T21:00:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.646Z"},{"id":"NVI-00003687","kind":"vulnerability","title":"Craft CMS: Entries Authorship Spoofing via Mass Assignment","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2xfc-g69j-x2mp","CVE-2026-28781"],"plain_summary":"OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.9.0-beta.1 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.17.0-beta.1 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-4995a1133558b45cdcc25441857f6ee6"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.388%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32897. Missing scores are unknown.","source_id":"sr-4995a1133558b45cdcc25441857f6ee6"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-47747ad4a55a11dadd6765ba45033175","url":"https://github.com/advisories/GHSA-2xfc-g69j-x2mp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2xfc-g69j-x2mp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.646Z"},{"id":"sr-4995a1133558b45cdcc25441857f6ee6","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-28781","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Description\nThe entry creation process allows for **Mass Assignment** of the `authorId` attribute. A user with \"Create Entries\" permission can inject the `authorIds[]` (or `authorId`) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others.\n\nNormally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively \"spoofs\" the authorship.\n\n## Proof of Concept\n### Prerequisites\n- A user account with \"Create Entries\" permission for a section.\n- Victim's account ID (e.g., `1` for the default Admin).\n\n### Steps to Reproduce\n1. Log in as the attacker\n1. Navigate to the \"Entries\" section and click \"New Entry\"\n1. Fill in the required fields\n1. Enable a proxy tool (e.g., Burp Suite) to intercept requests\n1. Click \"Save\" & Intercept the request\n1. In the request body, add a new parameter to the body params: `&authorIds[]=`\n1. Forward the request\n1. Log in as an admin / as with the victim account\n1. Go to entries & Observe the newly created entry is","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.9.0-beta.1"]},{"certainty":"source_listed","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Description\nThe entry creation process allows for **Mass Assignment** of the `authorId` attribute. A user with \"Create Entries\" permission can inject the `authorIds[]` (or `authorId`) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others.\n\nNormally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively \"spoofs\" the authorship.\n\n## Proof of Concept\n### Prerequisites\n- A user account with \"Create Entries\" permission for a section.\n- Victim's account ID (e.g., `1` for the default Admin).\n\n### Steps to Reproduce\n1. Log in as the attacker\n1. Navigate to the \"Entries\" section and click \"New Entry\"\n1. Fill in the required fields\n1. Enable a proxy tool (e.g., Burp Suite) to intercept requests\n1. Click \"Save\" & Intercept the request\n1. In the request body, add a new parameter to the body params: `&authorIds[]=`\n1. Forward the request\n1. Log in as an admin / as with the victim account\n1. Go to entries & Observe the newly created entry is","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.17.0-beta.1"]}],"null_published_at":"2026-10-31T23:18:17.259Z","source_updated_at":"2026-03-04T18:48:54.065Z","source_disclosed_at":"2026-03-03T21:00:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.646Z"},{"id":"NVI-00003687","kind":"vulnerability","title":"Craft CMS: Entries Authorship Spoofing via Mass Assignment","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2xfc-g69j-x2mp","CVE-2026-28781"],"plain_summary":"OSV carries this publisher advisory for craftcms/cms, craftcms/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.9.0-beta.1 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 4.17.0-beta.1 for craftcms/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-47747ad4a55a11dadd6765ba45033175","url":"https://github.com/advisories/GHSA-2xfc-g69j-x2mp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2xfc-g69j-x2mp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.646Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Description\nThe entry creation process allows for **Mass Assignment** of the `authorId` attribute. A user with \"Create Entries\" permission can inject the `authorIds[]` (or `authorId`) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others.\n\nNormally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively \"spoofs\" the authorship.\n\n## Proof of Concept\n### Prerequisites\n- A user account with \"Create Entries\" permission for a section.\n- Victim's account ID (e.g., `1` for the default Admin).\n\n### Steps to Reproduce\n1. Log in as the attacker\n1. Navigate to the \"Entries\" section and click \"New Entry\"\n1. Fill in the required fields\n1. Enable a proxy tool (e.g., Burp Suite) to intercept requests\n1. Click \"Save\" & Intercept the request\n1. In the request body, add a new parameter to the body params: `&authorIds[]=`\n1. Forward the request\n1. Log in as an admin / as with the victim account\n1. Go to entries & Observe the newly created entry is","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0-RC1; fixed 5.9.0-beta.1"]},{"certainty":"source_listed","source_ids":["sr-47747ad4a55a11dadd6765ba45033175"],"technology":"craftcms/cms","known_exclusions":[],"conditions_summary":"## Description\nThe entry creation process allows for **Mass Assignment** of the `authorId` attribute. A user with \"Create Entries\" permission can inject the `authorIds[]` (or `authorId`) parameter into the POST request, which the backend processes without verifying if the current user is authorized to assign authorship to others.\n\nNormally, this field is not present in the request for users without the necessary permissions. By manually adding this parameter, an attacker can attribute the new entry to any user, including Admins. This effectively \"spoofs\" the authorship.\n\n## Proof of Concept\n### Prerequisites\n- A user account with \"Create Entries\" permission for a section.\n- Victim's account ID (e.g., `1` for the default Admin).\n\n### Steps to Reproduce\n1. Log in as the attacker\n1. Navigate to the \"Entries\" section and click \"New Entry\"\n1. Fill in the required fields\n1. Enable a proxy tool (e.g., Burp Suite) to intercept requests\n1. Click \"Save\" & Intercept the request\n1. In the request body, add a new parameter to the body params: `&authorIds[]=`\n1. Forward the request\n1. Log in as an admin / as with the victim account\n1. Go to entries & Observe the newly created entry is","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0-RC1; fixed 4.17.0-beta.1"]}],"null_published_at":"2026-10-31T22:12:48.026Z","source_updated_at":"2026-03-04T18:48:54.065Z","source_disclosed_at":"2026-03-03T21:00:51.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:49.646Z"}],"next_cursor":null,"snapshot_revision":"42594"}