{"version":"2.1.268","anchor":"write-db-field-parameter-validation-tightened","canonical_anchor":"write-db-field-parameter-validation-tightened","heading":"write_db 'field' parameter validation tightened","tier":"notice","area":"Artifacts DB","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/write-db-field-parameter-validation-tightened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### write_db 'field' parameter validation tightened\n\nwrite_db's str_replace 'field' parameter now has a stricter length and character check\n\n**What**\n\nThe `field` parameter used by `write_db`'s `str_replace` operation used to be validated with a simple regular expression. It's now checked against an explicit length bound of 1 to 200 bytes plus a named rule: the field must name a single top-level key, with no dots, slashes, brackets, quotes, backslashes, control characters, or invisible formatting characters, and it can't be the reserved `__name__` key.\n\n**Why**\n\nThis closes off ways a malformed or crafted `field` value could reference something other than a simple top-level key, such as by using path-like separators or hidden characters.\n\n- Area: Artifacts DB\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}