> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/knowledge/forge/exploits/applying-inaccessible-object-properties.md).

# Applying Inaccessible Object Properties

{% hint style="warning" %}
This article is a stub. You can help TSG Forge Wiki by expanding it.
{% endhint %}

{% content-ref url="/pages/GM351bN7cTWtKE8mn777" %}
[Submitting Content to the Wiki](/community/contributing-to-tsg-forge-wiki/submitting-content-to-the-wiki.md)
{% endcontent-ref %}

Twitter video of the exploit being performed: <https://x.com/_Okom/status/1758653501914116288>

The way this bug works is by first selecting the object you want to transfer the properties from and closing the Forge menu. Then selecting the desired object and manually opening the menu at the same time. It should then still display the properties of the previous object.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.thescriptersguild.com/knowledge/forge/exploits/applying-inaccessible-object-properties.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.