AI Translate
The module does not properly check access rights on related fields or referenced items during translation. A user with an ordinary account could translate items they should not have access to. They could not read or update the affected items in other ways.
- Who could do thisOnly someone with a login on your site.
- Does it apply to youAny site using this module.
- Has it been used in attacksNo sign of it.
- How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.
Tell your developerUpdate AI Translate to 1.3.2 or 1.4.1, whichever branch you are on.
For developers: what the fix changed
The fix replaces the generic permission check on the translation route with a custom access callback in `AiTranslateController::checkAccess` to ensure the user has update access to the entity and translation create access. It also adds field-level view access checks in `TextExtractor` and referenced entity view and update access checks in `ReferenceFieldExtractor`.
Also in this release The release also adds translation result caching, support for translating the 'description' field in custom menu link content, GitLab CI configuration, and documentation.
.cspell-project-words.txt+11 −0.gitlab-ci.yml+73 −0.gitlab/issue_templates/bug_report.md+69 −0.gitlab/issue_templates/feature_request.md+48 −0.gitlab/issue_templates/plan.md+75 −0.gitlab/issue_templates/support_request.md+64 −0.gitlab/issue_templates/task.md+72 −0.gitlab/merge_request_templates/Default.md+58 −0README.md+4 −0ai_translate.module+9 −37ai_translate.post_update.php+24 −0ai_translate.routing.yml+2 −1 fix