Use the owner-supplied general contact service@kimorapro.com to request a private reporting route. This documentation does not establish a security-specific mailbox, confirmed delivery, response-time SLA or a public product Directory support forum.
Prepare a minimal private report
Identify the affected package, exact version/build and environment. Include prerequisites, the smallest reproduction with synthetic data, expected/actual behavior, impact and UTC timestamps. Distinguish an observed authorization or data-integrity failure from a configuration hypothesis.
Use stable placeholders for sensitive values so maintainers can correlate steps without receiving real credentials. Include a redacted screenshot or relevant log excerpt only when it helps reproduce the issue. If you have a proposed mitigation, describe its ownership and limitations.
A private repository advisory is appropriate only when the owner has supplied or confirmed that repository/channel. Do not invent a reporting URL or assume access to a private GitHub project.
Keep exploitable details and personal data private
Do not publish working exploit instructions in a public issue, forum, review or Documentation comment. Do not attach production database dumps, guest names/emails, cookies, passwords, payment/license secrets, activation tokens, signed booking links, full iCal feeds or webhook signatures.
If a secret may already be exposed, record the incident time and coordinate rotation through its owning operator. Share the redacted identifier and outcome rather than the live token. Preserve evidence without copying unnecessary personal information.
Contain active incidents
Restrict the affected access or integration, preserve audit/financial/inventory records and test mitigations on an isolated copy. Do not delete bookings, external blocks, ledger rows or privacy history to demonstrate impact or make an indicator disappear.
Avoid changes that destroy evidence before the operator has captured a private recovery set. A theme rollback, gateway disablement and salt rotation have different effects; choose the smallest relevant containment action and verify it.
Follow up with verified outcomes
Keep a timeline of evidence, containment and tests. Do not promise a public fix date or claim a vulnerability is resolved from source review alone. Full runtime reproduction, denied-access regression and actual deployment/readback are separate checks.
For recovery planning see backup and incident response; for ordinary configuration issues see support escalation.
