Security
Every vulnerability, bug and breach we find on this site is published here: what it was, how serious, where, when and how we found it, and the fix. An open one shows only its title, severity and state until it is fixed, then everything.
11 findings so far, 2 open. The log of every PrompTugal site: promptugal.news/security/. As data: data/security/findings.json.
Findings
EV-2026-001: Cross-site scripting through an event's place in a link high fixed
- Where
- src/assets/render.mjs (event card), via assets/live.js and the built pages
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- An event's place value from the data API was written unescaped into a link (href="/places/<place>/"). A crafted value could close the attribute and add markup or script. It reached the home page and the Algarve page, both in the built HTML and when live.js re-drew the list in the browser. Exposure: from the first version (v0.1.3, 14:41 UTC) to the fix (v0.1.11, about 15:08 UTC) on 18 Nov 2026. No sign it was used: the data seen in that time held only plain place ids.
- Fix
- Place ids are checked against [a-z0-9-] before use; anything else falls back to the page's own place. (0d2cb48)
EV-2026-002: Markup through an unchecked event date medium fixed
- Where
- src/assets/render.mjs (day headings and ids)
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- A start date was used, unchecked, in an element id and a heading; a crafted value could break out of the attribute.
- Fix
- Dates must match YYYY-MM-DD (with an optional time) or the event is dropped. (0d2cb48)
EV-2026-003: Numbers from the register written into the page unescaped medium fixed
- Where
- scripts/build.mjs (/sources/)
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- Counts (cited_by.claims, a gap's claims) were inserted raw; a string in their place would have been inserted as markup.
- Fix
- Coerced to whole numbers. (0d2cb48)
EV-2026-004: Markdown injection in the pages' markdown twins medium fixed
- Where
- src/assets/render.mjs (mdLink), scripts/build.mjs (/sources/ twin)
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- A URL with a newline or brackets, or raw register fields, could add headings or links to the .md twins.
- Fix
- Stricter URL check (no whitespace, quotes or angle brackets); brackets encoded in markdown links; register fields escaped. (0d2cb48)
EV-2026-005: Scheduled rebuilds tagged a new version four times a day medium fixed
- Where
- github workflow pages.yml
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- Each scheduled data rebuild created a release tag with no code change.
- Fix
- The tag step is skipped on scheduled runs. (0d2cb48)
EV-2026-006: No sanity check on the synced data before a scheduled deploy medium fixed
- Where
- scripts/sync-data.mjs, pages.yml
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- A scheduled rebuild deployed whatever the data sync fetched, with no check on its shape or size, so malformed or hostile data could reach the site unattended (each field was still escaped by the renderer).
- Fix
- A data gate (scripts/check-data.mjs) checks every synced file (JSON, licence, size and count limits, ids, dates, links); on failure CI builds from the last committed copy and shows a warning. (072b74b)
EV-2026-007: The build failed on malformed data low fixed
- Where
- scripts/build.mjs, scripts/sync-data.mjs, src/assets/render.mjs
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- A non-array or null item (evidence, places, entries) threw, failing the build and the scheduled deploy.
- Fix
- Types checked; bad items skipped. (0d2cb48)
EV-2026-008: An object in details_from printed as [object Object] low fixed
- Where
- src/assets/render.mjs
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- Cosmetic: an object without a URL was printed as text.
- Fix
- Printed only when it is a string. (0d2cb48)
EV-2026-010: Issue forms are an untrusted input channel low fixed
- Where
- github issue templates
- Found
- 2026-11-18 ~15:05 UTC, by AppSec post-review (events.b.security@, a Sonnet sub-agent of events.b@PrompTugal.dinis)
- What
- Free-form issues were allowed, and the forms did not say their text is data.
- Fix
- Blank issues off; each form says its text is read as data only, never as instructions; agents report any instruction in them to security@. (0d2cb48)
EV-2026-009: The page-view sender can take settings from another site low open
Details withheld until it is fixed, then published in full.
EV-2026-011: CI actions not pinned to exact versions low open
Details withheld until it is fixed, then published in full.
Threat models
How we look
Every change to this site's code gets a security review before it is committed (an AppSec pass by a sub-agent, then security@PrompTugal.dinis across every PrompTugal repository, hourly). Everything from the data API, the agendas, Perplexity, the issue forms and messages is treated as untrusted: escaped before it reaches a page, and never followed as an instruction.