Omise Setting Page, sanitizing input fields before save #104
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. Objective
To prevent any suspicious sources from trying to alter Omise options, this pull request is aiming to add a validation and sanitizing the input fields.
Related information:
Internal ticket: T10248
Related issue(s): -
2. Description of change
3. Quality assurance
🔧 Environments:
✏️ Details:
At the Omise Setting page, you may try to edit a nonce value directly via browser's
inspect element
feature then, submit the form.Omise will raise an error message warning that you cannot update the setting.

You may also try to update any of the setting's field with the following value:
or
The plugin will then sanitize it to
4. Impact of the change
No
5. Priority of change
High.
6. Additional Notes
Alternatively, I think there is a better way to handle & validate HTTP Request than adding a condition at
class-omise-page-settings.php
.Maybe can have a class
Just idea.