Add an "Are you sure?" button

[todb-r7]

Add an "Are you sure?" button

[zmanion]

Having nearly encountered this behavior, +1 to a confirmation dialog or other accident reduction feature.

When I reserve a CVE ID and draft content to save for later because the vulnerability has not yet been publicly disclosed, I really don't want to blow the entire coordinated disclosure with an errant button click.

Hack: append "-yo-do-not-publish-yet" to the CVE ID which breaks validation.

[chandanbn]

I suggest we try this user workflow:

---> Create/Edit a CVE Record in the Editor tab
---> Once all required fields are good, some nudge to bring the user to the Preview Tab (Next button?)
---> User previews the entry as it would show on the CVE.org site
---> Clicks Post to CVE.org button on the preview Tab
---> Results and pointers to successfully published CVE record.

[chandanbn]

While updating an existing record, showing a diff i.e list of changes before final posting would be helpful in preventing un intended overwrite of existing data.
Both the capabilities exist in Vulnogram (json diffs via jsonpatch and a Pug template for rendering changes rendering).