Unpacking the Drama: When Akshaye Khanna Allegedly Wanted a Writer Fired from 'Section 375'
Share- Nishadil
- December 29, 2025
- 0 Comments
- 3 minutes read
- 5 Views
The Shocking Backstory of 'Section 375': Akshaye Khanna's Demand to Sack Writer Manish Gupta Over a Past Script Dispute
Dive into the surprising backstage drama of 'Section 375,' where acclaimed actor Akshaye Khanna reportedly insisted on the removal of its writer, Manish Gupta, due to a bitter past script dispute. Discover how a clash over creative differences nearly derailed a critically important film.
Remember Akshaye Khanna's powerhouse performance in 'Section 375'? That film, lauded for its gritty portrayal of a sensitive subject and its intense courtroom drama, actually had quite a bit of drama brewing behind the scenes – far from the legal battles we saw unfold on screen. It turns out, a rather intense conflict involving Khanna and the film's writer, Manish Gupta, almost saw Gupta unceremoniously dropped from the project.
The air, it seems, was thick with tension even before filming properly began. According to various reports and what has been widely discussed within industry circles, Akshaye Khanna, known for his discerning choices and intense portrayals, allegedly put his foot down, demanding that Manish Gupta, the very person who penned the gripping screenplay for 'Section 375,' be removed from the project. And why such a strong reaction, you ask? Well, it wasn't about the script for 'Section 375' itself, but rather a bitter dispute stemming from an entirely different project that predated it.
Khanna's alleged words were reportedly quite strong, expressing deep betrayal: "Usne bahut hi ghatiya harkat ki hai mere saath" – essentially, "He has done a very cheap act with me." A heavy accusation, no doubt, hinting at a profound breach of trust that had clearly lingered in the actor's mind, making him unwilling to collaborate again with Gupta, even on a new film as promising as 'Section 375'.
But, as with most disputes, there are always two sides to the story, aren't there? Manish Gupta himself offered a different perspective on their past collaboration. He recounted how, during an earlier project – reportedly 'The State of Siege: Temple Attack' – Akshaye Khanna had initially approved his script. However, just a week later, the actor supposedly changed his mind, requesting a complete rewrite. Fair enough, creative processes evolve. But then, according to Gupta, Khanna allegedly refused to return the original script, despite repeated requests. Worse still, Gupta claimed his original work was later shared with other writers without his permission, leaving him feeling, understandably, quite wronged and protective of his intellectual property.
Enter producer Kumar Mangat Pathak, the man tasked with navigating this high-stakes creative standoff. It was, undoubtedly, a tricky situation. On one hand, you had a highly respected actor, Akshaye Khanna, clearly upset and firm in his stance. On the other, you had the writer, Manish Gupta, whose script for 'Section 375' was, by all accounts, central to the film's vision and impact. Mangat, recognizing the sheer brilliance and vital role of Gupta's screenplay in bringing 'Section 375' to life, reportedly played a crucial mediating role. He must have done some serious convincing, emphasizing to Khanna that, regardless of past issues, Gupta's contribution to this particular film was indispensable for its success.
Ultimately, good sense (and perhaps the sheer power of a strong script) prevailed. Manish Gupta remained on board, and 'Section 375' went on to achieve critical acclaim, lauded for its brave narrative and performances, Akshaye Khanna's included. It's a fascinating peek into the often-turbulent waters of filmmaking, reminding us that even the most polished final products can have layers of intense human drama behind their creation. Creative differences are par for the course, but sometimes, they come pretty close to derailing something truly special.
Disclaimer: This article was generated in part using artificial intelligence and may contain errors or omissions. The content is provided for informational purposes only and does not constitute professional advice. We makes no representations or warranties regarding its accuracy, completeness, or reliability. Readers are advised to verify the information independently before relying on